These are necessary to get the framework usable with modern web requirements.
It's best to rely on libsoup features in order to minimize the work on implementation and testing.
- cookies using Soup.Cookie (arteymix)
- session with Gee.Map and cookie
- streamed bodies (arteymix)
- FastCGI support (arteymix)
- HTTP query using Soup.URL (arteymix)
- x-www-form-urlencoded parsing using Soup.Form (arteymix)
- documentation using valadoc
- register types at dynamic time using an Map
- optional/nullable route parameter
- regex literal in route declaration
- Simple view engine based on CTPL. (antono)
- Define View engine interface (antono)
- JSON view engine. See json generation in Vala
- CTPP2 integration (need patching CTPP2)
- Clearsilver integration (see post)
- migrate to vsgi
- Avahi support for mdns local addresses like http://cool-app.local
- Logger with switchable backends (file, redis, dbus for ide integration).
- Automagical configuration and build system for app develpers (autotools is too complex)
- Integration with Nemiver
- Integration with Perfkit
- Integrate somehow with Valgrind
- integrate libgda (see post)
- U1DB
- vapi for mongo-glib
- integrate couchdb-glib
- vapi for hiredis
- charango RDF storage via Tracker
- midgard2 integration
- GObject Content Repository
- (lua) make luapanic safe for app (occurs in luajit under heavy load)
- (scheme) vapi for guile
- (javascript) integrate javascriptcore or V8 as (java)scripting engine. see valum/script/lua.vala for details
- (ruby) try to make it working with ruby.vapi
- On migration of MainLoop to epoll
- http://ctpl.tuxfamily.org/
- https://github.com/apmasell/vapis/blob/master/fcgi.vapi
- http://code.google.com/p/sqlheavy/wiki/UserGuide
- https://gitorious.org/libpeas-vapi ?
- https://github.com/apmasell/vapis
- https://github.com/gorilla3d/Pawalicious/blob/master/server.vala
- https://github.com/lgunsch/zmq-vala
- https://github.com/fengy-research/libyaml-glib