Simon and Jacob,
I'm interested in this for a couple of reasons. ...
These are among the reasons I started Aspen.
I think there are three layers to look at here:
1. core HTTP library -- wsgiref, cherrypy.wsgiserver, etc.
2. server -- UI for the library (cli, config files, etc.)
3. web framework -- 'nuff said
Seems to me that the frameworks could/should cooperate at least
on #1, and maybe on #2.
Aspen is really about #2. I tried to design Aspen to be usable
for all kinds of Python web frameworks, whether Python-centric or
filesystem-centric. I'd be willing to talk about implementing the
filesystem-centric parts separately if that might mean a wider
audience for Aspen. But it may also truly be the case that
there's not enough value in cooperating on #2.
chad
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django
users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
