On Tue, 30 Mar 2010 19:41:40 -0600, Andre Carregal
<carre...@fabricadigital.com.br> wrote:
Also, what is CGILua exactly? Judging by the name and what I can
decipher of
the description, it sounds like a CGI WSAPI connector, which WSAPI
seems to
provide anyway.
CGILua was the first use of Lua for web development, back in 1996. By
then it was a bind of CGI therefore the name. As the Kepler project
started evolving first SAPI then WSAPI based solutions, the CGILua
style (PHP like page generation) got less and less attention.
So, CGILua was a sort of proto-Kepler Project, from before separate
libraries were used to handle each aspect of development?
CGILua is not tied to CGI anymore (since it now uses WSAPI), but the
name remained. This surely didn't help much on the communication
side...
I guess what I'm saying is, I can't see what CGILua's "Lua Scripts"
functionality, as demonstrated under
http://keplerproject.github.com/cgilua/manual.html#scripts, adds to a bare
WSAPI script like samples/hello.lua to necessitate intermediary layers
like SAPI, and what it provides for
http://keplerproject.github.com/cgilua/libraries.html that keeps them from
standing alone.
I think there's still, at its core, a thin layer that CGILua provides
around WSAPI (such as handling HTTP details like status codes and headers
and removing the need to design an iterator), but going forward, the way
to fill this role, from a design standpoint, should be to make a new
library designed with only these goals in mind, without the historical
ties to CGI and double-abstraction against WSAPI.
Also, why does the main page say that CGILua is no longer supported if
it
was just updated a little over a week ago?
The changes have been mostly adaptations to changes in WSAPI (which is
below SAPI, used by CGILua). While some still like the CGILua PHP like
style, there is no one directly involved with the development of
improvements for CGILua.
What is SAPI, and what does it accomplish? This is one of the big points
of confusion for me. I REALLY can't understand the role of SAPI, except
that it seems to have been written to bridge the gap between the original
design of CGILua and WSAPI.
Fabio and I have been working on a intermediary level (to sit between
WSAPI and modules like Orbit or CGILua) that will absorb part of the
current code duplication on those modules, so CGILua could eventually
be refactored into a simpler module.
So we are looking for voluntaries to continue the evolution of the
currently non maintained modules. :o)
André
I could volunteer to "refactor" CGILua into smaller libraries if I had a
full understanding of what CGILua still provides that hasn't been
superseded by newer libraries.
Also, why isn't http://www.tecgraf.puc-rio.br/~tomas/htk/ a Kepler project?
_______________________________________________
Kepler-Project mailing list
Kepler-Project@lists.luaforge.net
http://lists.luaforge.net/cgi-bin/mailman/listinfo/kepler-project
http://www.keplerproject.org/
