This week has been spent on finishing the basic plugin api documentation as well as creating a prototype.
A blog post that I started last week that motivated and described the core plugin api changes needed to support future protocols is finished. It describes the assumptions I've made about HTTP-like protocols and then describe a plugin api that tries to avoid making other assumptions. Together with this blog post I've developed a working prototype of the plugin api and also a static file plugin. The code is based on a branch of monkey for now as some changes are needed in monkey core for the new api to work seamlessly alongside the current api. It uses mostly already existing core functions to implement the api, and will therefore not allow multiple protocols yet. The blog entry permanent uri is [API changes](https://lotrax.org/gsoc/api-changes-in-detail.html) The prototype is available at [github](https://github.com/ksonny/monkey/tree/plugin_nex://github.com/ksonny/monkey/tree/plugin_next) Now that I have a plugin api that does not make assumptions that only hold for HTTP/1.*, I have started to develop a minimal amount of changes needed in monkey core to support multiple simultaneously served protocols with the new api. The first of these changes is the addition of a pending data interface, `mk_queue.c`. Permanent uri of post: [GSoC Week 3](https://lotrax.org/gsoc/gsoc-2013-status-future-protocols-week-3.html) -- Sonny Karlsson _______________________________________________ Monkey mailing list [email protected] http://lists.monkey-project.com/listinfo/monkey
