I have a pile of OS's running, here, for all sorts of reasons. Yes, I
could, and have, deploy (and develop) on one of several linux boxes that I
have running you-name-it with whatever desktop environment is on that box.
In some cases, there are issues where some other piece of gear is OS
limited t
Mike Kerner wrote:
> I have a bunch of stacks that run, constantly, doing a variety of
> things.
> Some are even run as daemons by other processes. So, I suppose they
> could run in server, but I'm still unclear as to why I would choose
> to do that.
LC Server is a great tool for mixing LiveCode
Mike,
I like not having to leave a session logged in just to run a daemon, or a
LC instance. If there is a power failure, my server reboots, and scripts
are available. Otherwise, after a power failure, I have to log in and
start the daemons. It is speedy, but for my applications (in-house), wha
Roger,
But why do it in server instead of just having another instance of LC
running, sitting off in its own space? Since you don't have a message box,
any output is going to require email, push, or writing to a file. Is
Server just a beast for speed? You can't possibly save enough memory from
a
Hey Mike,
Most daemons I have built with LC will poll a folder at a set time
interval, and act accordingly dependent upon what it finds in the folder.
A polling interval set too short can make the server slower. Setting it
too long makes the users complain about waiting 30 seconds or a minute.
Us
I have a bunch of stacks that run, constantly, doing a variety of things.
Some are even run as daemons by other processes. So, I suppose they could
run in server, but I'm still unclear as to why I would choose to do that.
--
On the first day, God created the heavens and the Earth
On the second d
