thanks to you, you should expect more feedback within the week, have a nice weekend.
On Fri, Mar 30, 2012 at 6:22 PM, Nicolas Pépin Perreault <[email protected]> wrote: > I've updated my proposal based on your comments, and with the idea in mind > that what I would be working on is now a Duda package. Thanks for the > feedback! > > > On 29 March 2012 14:01, Eduardo Silva <[email protected]> wrote: >> >> On Wed, Mar 28, 2012 at 10:32 PM, Nicolas Pépin Perreault >> <[email protected]> wrote: >> > Hi, >> > >> > For the Lua Integration idea, the description is as follows: >> > >> > "The idea of this project is to extend Monkey to add Lua support, so >> > then >> > Lua scripts can be executed to process and render responses for HTTP >> > requests." >> > >> > From what I understand, the goal here is thus to have a Lua interpreter >> > as a >> > Monkey plugin to allow developers to serve dynamic content through Lua >> > scripts. What I'm wondering is, if this is strictly the goal, then >> > wouldn't >> > it be more beneficial to have Lua be a package in Duda? That way web >> > services could use the interpreter to serve dynamic content, and Lua >> > bindings could be provided for all features of the Duda (JSON, SQLite, >> > eventually Redis, MySQL, etc.). The only reason I would see for Lua to >> > be >> > its own plugin, is if we wanted to use Lua scripts for other purposes, >> > such >> > as debugging, testing, logging, etc. - in other words, functionalities >> > not >> > relating to web services. Maybe I'm wrong though, or I misunderstood the >> > project description, or I don't understand what the purpose of Duda is. >> >> Thats a good point that could start with a research of pros and cons >> of what is the best way to follow, this needs some discussion. >> >> > >> > Similarly, the idea mentions evaluating and porting an existing library >> > like >> > Lua Web Tools (http://code.google.com/p/lua-web-tools). The library is >> > interesting, but is very big, tied to Apache and would narrow the >> > choices of >> > developers; maybe it would be more interesting to implement the Web >> > Server >> > API (http://keplerproject.github.com/wsapi/), such that Lua web >> > applications >> > using frameworks like Orbit (http://keplerproject.github.com/orbit/) can >> > run >> > in Monkey (as well as all other WSAPI enabled HTTP daemons. >> >> good one. agree. >> >> > >> > Finally, the point of defining an API for the Lua side is very vague; >> > does >> > this refer to how much of the Monkey API is exposed to Lua scripts (i.e. >> > Lua >> > bindings for Monkey), or does it refer to something closer to LWT (i.e. >> > providing a dynamic template engine and other functionalities for web >> > applications). That last part, if we couple Duda with the Lua plugin, >> > would >> > be simply just writing bindings for Duda packages, and allowing web >> > services >> > to use Lua to serve dynamic content. >> > >> > I have also submitted my proposal, so feedback on it is much >> > appreciated; >> > keep in mind it will be very subject to change after more discussion. >> >> we will provide you some public feedback shortly >> >> > >> > -- >> > - Nicolas Pépin-Perreault >> > >> > _______________________________________________ >> > Monkey mailing list >> > [email protected] >> > http://lists.monkey-project.com/listinfo/monkey >> > >> >> >> >> -- >> Eduardo Silva >> http://edsiper.linuxchile.cl >> http://www.monkey-project.com > > > > > -- > - Nicolas Pépin-Perreault -- Eduardo Silva http://edsiper.linuxchile.cl http://www.monkey-project.com _______________________________________________ Monkey mailing list [email protected] http://lists.monkey-project.com/listinfo/monkey
