You should never use 'send in time' or 'wait with messages' in LCServer.
Each http request starts up your LC server script anew - and you need
that request to be handled and the server-instance shut down as quickly
as possible. And the next http request will start up another, entirely
separate
I was playing around with Send In Time
with LC Server. It’s throwing an error
at me after it’s supposed to be all done
executing.
The reason I was playing with such things
is I want to be able to logoff any user that
hasn’t been using the website for a few
minutes when the system times out.
H
On 7/18/19 8:11 AM, dsc--- via use-livecode wrote:
Also...
If you have control of these sites and even if you use an ISP DNS service, you
can add a secondary DNS IP address, perhaps a public recursive name server such
as the Google Public DNS (8.8.8.8). This will add a robustness without
upg
Not to put too fine a point on it but that gives me the heebie jeebies. There
are ~5000 instances of the app. The dev can't control what the ISP of the
server does, or if the hosting company goes out of business or gets bought out.
Although rare, an ISP CAN alter the public IP subnet. It happene
Also...
If you have control of these sites and even if you use an ISP DNS service, you
can add a secondary DNS IP address, perhaps a public recursive name server such
as the Google Public DNS (8.8.8.8). This will add a robustness without
upgrading the software.
If you don't manage those, you
