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.
Exactly our view. CGILua can be considered a PHP like solution, while
Orbit would be a MVC based solution and Sputnik another different
approach. While WSAPI was the first round of refactoring to unite
those approaches, MK (the new module Fabio mentioned) is the second
iteration of the same rationale.
MK will handle dispatching, authentication, caching and form handling.
Orbit is already being refactored to use it (reducing a lot of its
current code base), but Sputnik and CGILua could also eventually
decide to use at least some part of MK.
One advantage of paving the road with a module like MK is that
different frameworks can share the basic stuff, allowing for better
interoperability.
I'm not sure I understand- does MK use WSAPI, or is it a complementary and
separate layer?
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.
Let me know if now its role is clear for you.
It's a predecessor to WSAPI that is kept around because CGILua uses it?
_______________________________________________
Kepler-Project mailing list
Kepler-Project@lists.luaforge.net
http://lists.luaforge.net/cgi-bin/mailman/listinfo/kepler-project
http://www.keplerproject.org/
