Great! So glad you got to a successful conclusion.
Alex
Sent from my iPhone
> On 25 Jul 2019, at 17:12, Rick Harrison via use-livecode
> wrote:
>
> Hi Alex,
>
> The solution turned out to be easier with no time checks involved.
>
> I noticed that one of my variables ends up being blank whe
Hi Alex,
The solution turned out to be easier with no time checks involved.
I noticed that one of my variables ends up being blank when the
server times out. So when the user attempts to do something,
the destination webpage performs a check at the beginning of
the code to see if the variable i
On 19/07/2019 14:28, Rick Harrison via use-livecode wrote:
The following is a link to the javascript stuff I had referred
to before. I just want a clean LC way to do the same thing.
https://stackoverflow.com/questions/9564602/how-to-know-browser-idle-time?noredirect=1&lq=1
Sorry to be the be
Hi Alex,
> On Jul 18, 2019, at 6:55 PM, Alex Tweedly via use-livecode
> wrote:
>
> 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
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
