[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: Kepler 1.1 Status
- From: Fabio Mascarenhas <mascarenhas@...>
- Date: Fri, 27 Apr 2007 14:40:37 -0300
Hi,
André got things a little mixed up. :-)
On Apr 27, 2007, at 11:52 AM, Andre Carregal wrote:
On 27/04/2007, at 11:32, Bertrand Mansion wrote:
Is it possible to download the blog source code, along with all
the required modules to make it work ?
Yes, from http://www.lua.inf.puc-rio.br/svn/lablua/orbit_blog/trunk/
but if you are interested in helping us get there I'd ask you to
join the Kepler list. :o)
The URL above is wrong. The blog example is part of Orbit, at
http://www.lua.inf.puc-rio.br/svn/lablua/orbit-2.0/trunk
It's inside samples, and includes a db filled with random data.
Depends on WSAPI (http://www.lua.inf.puc-rio.br/svn/lablua/wsapi/
trunk) and LuaSQL/SQLite3 (fetch the HEAD of LuaSQL's repository at
LuaForge), and obviously Xavante (just install the Kepler base!).
If Kepler is going the WSGI road and Orbit is going to be the
"recommended" way to develop web applications, this blog
application would probably be a good example to understand the
concepts, at least for me... The WSAPI implementation I have seen
here <http://www.lua.inf.puc-rio.br/svn/lablua/wsapi/trunk/src/>
doesn't really look like WSAPI, unless I didn't grasp the concept.
Is this what you will use in place of WSAPI or is there another
implementation planned ?
http://www.lua.inf.puc-rio.br/svn/lablua/wsapi/trunk is not an
implementation of WSAPI per se. I will probably move Orbit/Xavante's
wsapihandler.lua to there eventually, as well other WSAPI handlers as
they appear. The WSAPI repo currently houses the Request/Response
helpers (which Orbit uses), as André says below..
Hum... maybe there is another WSAPI that we were not aware of. Are
you refering to some already existing thing? Sorry if this sound
stupid, but WSAPI for us is just a name we came to when refering to
the Web Server API.
Our view of WSAPI is of a filter based API that abstracts the
communication with the web server. Over that filters there are
helper modules that implement Request and Response classes. This is
what you saw at that SVN trunk.
Just keep in mind that all of this WSAPI/Orbit/Blog stuff is
inteded for Kepler 1.2, not for the next release of Kepler (1.1) on
LuaForge.
Thanks for asking
André
--
Fabio