[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: RES: CGILua future
- From: David Burgess <dburgess@...>
- Date: Fri, 26 Nov 2004 00:04:07 +1000
Seems a very sane approach to me.
> what i'm thinking now is to simplify things radically: i'll take just the
> fastcgi launcher of CGILua, and replace the lua-side with a minimal loop. to
> keep different applications separate, i'll run a different launcher process
> instance for each application (i think the apache .conf lets me do it easily)
> that means that each web app will have it's own lua state; one that doesn't go
> away after each request.
> on this environment, a small API would let the app register scripts referenced
> by the URL, and state objects referenced by a session cookie. no
> (de)serializing needed unless the app wants to make 'permanent' records (to a
> SQL db, usually)
> does this sound more Lua-like?