Thanks Andre - good call. Following others’ reminders of the single-threaded nature of LCS, I’m trying to rethink data flows as on-demand, to avoid all background tasks. Best, Keith
> On 30 Nov 2018, at 12:10, Andre Alves Garzia via use-livecode > <use-livecode@lists.runrev.com> wrote: > > Keith, > > >> The examples in the dictionary look potentially useful for a couple of >> lightweight activities I’d like to have ticking-over in the background on my >> LC Server, pending page visits. > > You shouldn't have the CGI engine hogging up like that, thats not how web > stuff is supposed to work. First, Apache (or whatever you're running) will > kill the process after some seconds if it fails to exit on its own. Second, > it is a waste of resources. Imagine that you have this running for every > request that is made, so each time a user requests your site, your LC Server > engine hangs in the background for a while, hogging up system resources. > > LC Servers should reply as fast as possible and then exit. If you need a long > running process to do some administrative stuff regularly, then, consider > building a little script and running that as a real proper cronjob on the > server, not tied to visits. > > Cheers > > andre > > > > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
