Making Dylan viable for small web applications?

Hello,
I have a couple of ideas for small web applications that I want to develop using
Dylan. I'm not sure about the state of http-server so I'm asking you, if something
is outdated and/or you want it changed I think it's a good opportunity to discuss
it here before working on it.

By looking at projects like Lua's Lapis (http://leafo.net/lapis/) or Python's
Flask and with a quick chat with Bruce I came up with a list of components we
need:

* A web-server, with this I mean the usual routing stuff plus handling session etc.
* Template engine, I know someone is working on it so we should look into finishing
  and/or integrating it with the server
* Some kind of SQL abstraction layer, at first only supporting SQLite and
  PostgreSQL would be fine. I'd also like a light ORM, but I think I'm in the
  minority here.

Then we need to figure out to make this components work well together.

Finally, I'd love for the webserver to be extensible, so for example we would need
to write a session-management plugin only once. Bruce talked about adopting a
middleware architecture, but I forgot about it now.

So, what do you think?

-Francesco