Hi Stuart
So, CGILua was a sort of proto-Kepler Project, from before separate libraries
were used to handle each aspect of development?
CGILua was developed for Lua 3 :-) At that time there was no
standard way to load binary libraries for Lua and (I think) PHP didn't
exist :-) The Kepler Project started many years later and at that time
we tried to separate aspects of the web server from the CGILua layer.
Then SAPI was born. Kepler 1.0 was developed for SAPI (IIRC). WSAPI
appeared after a while but since there are some CGILua users around
(me, at least!) they granted compatibility.
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 this is just a compatibility issue.
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.
I would say that SAPI is an evolutionary step to WSAPI :-)
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.
Now I am not dedicated to this project, but I think I could help.
Also, why isn't http://www.tecgraf.puc-rio.br/~tomas/htk/ a Kepler project?
I don't know. I think there are no HTK users out there :-) But
if you're interested, I can build a rockspec for it.
Regards,
Tomás_______________________________________________
Kepler-Project mailing list
Kepler-Project@lists.luaforge.net
http://lists.luaforge.net/cgi-bin/mailman/listinfo/kepler-project
http://www.keplerproject.org/
