lua-users home
lua-l archive

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

On Jan 5, 2012, at 8:02 PM, Gé Weijers wrote:

> It depends on the application, if it's a single long-lived process in stead
> of (say) a CGI program the issue becomes more pressing.

Sure thing. So many choices, so little time.

On the simplicity of, say, CGI:

"With my setup, there are no servers (other than inetd).  Everything runs
on-demand.  With no servers running, that means there are no servers to
crash and require restarting, no servers to configure, no servers to pick up
performance problems after running a few days due to memory fragmentation or
resource leaks, and no servers accidentally leaving open TCP ports that can
be attacked by miscreants.  Oh, and did I mention that my setup runs in a
chroot jail for additional security"
-- Richard Hipp, of SQLite fame

In any case, it would be nice if Lua had a more collision proof table implementation, but short of that, there is not much that one can do at the application level itself.

So there you go, one has the following options:

(1) Ignore the issue as not practically relevant
(2) Monkey patch the issue myriad of symptoms at the application level
(3) Fix the issue at Lua's level