1 There's lots of stuff yet to do!  This is just scratching the surface:
2 
3 ev:
4  - rework the internals; two queues is maybe too much
5  - timeouts support
6  - write more 'backends' for kqueue and epoll
7 
8 fcgi:
9  - I'm a sucker for running stuff behind httpd.
10 
11 http:
12  - find a way to associate custom data to a request for asynchronous
13    re-entering (and eventually free the custom data too!)
14  - notify unexpected disconnection when re-entering?  (i.e. notify the
15    route function when they set res.done = false)
16  - http keepalive?
17  - actually parsing headers.  do we want to expose all of them?
18  - parse body contents.
19 
20 http::session:
21  - a custom module for session handling would be nice.  Or just use
22    Authorization header and be done with it?
23 
24 http::websocket:
25  - another would be nice to have :)
26 
27 gemini:
28  - Yes, I'm serious!  A gemini module to serve stuff via gemini (w/
29    libtls bindings?) would be cool and probably fit shinsha well.
30 
31 sqlite:
32  - write the bindings.  Maybe drawing some inspiration from
33    https://github.com/crawshaw/sqlite (and the sqlitex subpackage)
34    which is my favourite sqlite binding for Go.
35 
36 template:
37  - write (how?) some kind of template processor with the asynchronous
38    http module in mind?