Hi,
On Sat, Mar 1, 2014 at 3:42 PM, 董凯 <[email protected]> wrote: > Hello, > > I am a graduate student of computer science in Canada. > I am very interested in the Lua Scripting Support idea in > your GSoC 2014 projects. I have gone through the "Getting > started" part briefly. Here I have some questions about the > project requirements: > > As mentioned in the idea description, the required monkey > plugin needs to interpret the Lua scripts to "perform different > administrative tasks and be able to hook callbacks different > HTTP events across the cycle". > > What does the "administrative tasks" include? Simply configure > the HTTP server when it gets started, or it should be able to > give orders to the HTTP server when it is running? > > on the administrative tasks area, it should cover a native Lua API calls to obtain server configuration, memory usage per worker, list running plugins, etc. Mostly read-only interfaces to get status from the server. > Does the " different HTTP events" mean the "accept connection"/ > "read socket"/"write to the socket"/... as described in the > networking APIs in Monkey plugins? > > I look forward to your reply. > > In Monkey a HTTP connection pass through different stages: 10, 20, 30, 40 and 50. On each one the Plugin core looks for plugins being hook to each stage, for more details refer to the link posted inside the getting_started section: http://swpd.github.io/blog/2013/05/18/monkey-http-daemon-internals/ regards, > Best, > Kai > > _______________________________________________ > Monkey mailing list > [email protected] > http://lists.monkey-project.com/listinfo/monkey > > -- Eduardo Silva http://edsiper.linuxchile.cl http://monkey-project.com
_______________________________________________ Monkey mailing list [email protected] http://lists.monkey-project.com/listinfo/monkey
