[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: Library for off-system
- From: Xico leite <xxleite@...>
- Date: Thu, 18 Mar 2010 14:30:30 -0300
thanks for information!
but wsapi needs to run over a server ... well, ill take a look first,
and also i have some headaches with cgi/fastcgi drives ...
any comments about the "persistence database"?
2010/3/18 Sam Roberts <email@example.com>:
> On Thu, Mar 18, 2010 at 10:08 AM, Xico leite <firstname.lastname@example.org> wrote:
>> plugin like lighttpd has, ill atach the "persistence database" and
>> "off-system library" on server process, so plugin will be a lua
>> metaclasse that will be loaded into server process...
>> cgi ... well when i ask on kepler list about it, they said that lua
>> pages runs under cgi...have u already take a look at server variables
>> well, i create a "lp" global var that have some methods like
>> "lp.header( name,value ), lp.cookie( ... ), lp.write( ... ),
>> lp.vars['??'] lp.req['??']" all pages need a header, cookie, something
>> to display, server variables and request variables ...
> But... this sounds like you are rebuilding wsapi:
> Which to my knowledge is what kepler uses to talk to its host env,
> which could be xavante, or other stuff.
> Are you sure you aren't confusing wsapi, the interface of which was
> designed to "look" a bit like CGI, and CGI itself?
> I don't mean to discourage you, you sound like you're having fun, but
> if you want to build a distributed content network, you might consider
> skipping the "build http server" stage, and get to the hard stuff!