Growler

ter interface. Currently I have no good way to do something like res.on('send-headers', cb) ~ (thinking res.events['send-headers'].add(cb)) with events as EventManager object. Maybe decorators here? - ETAGs - HTTP/2 - pytest-growler for automated fixtures - I don't think an admin panel is necessary (can't beat django) but would like some CLI tools for site creation, testing, and deployment. Renderer Explaination: (too many 'render' words) The author creates a RenderEngine as the actual middleware: app.use(MakoRenderer("/path/to/view")). All this middleware does is attach a callable Renderer object to res at res.render if it doesn't exist, then add itself to res.render - this allows multiple RenderEngines in the same app (if the author desires) - and none of them will clobber one another. Upon calling the Renderer: res.render('foo', data_obj), the callable scans through the engines until one with 'foo' is found, then the rendered text is sent. It's non-(obvious|trivial) situations like these I want in Growler proper (some batteries included) - the rest can be extensions. [0] https://github.com/pyGrowler/Growler/blob/dev/growler/middle...