On 3 Dec 2007, at 08:15, James Bennett wrote:
> At that point I'd wonder why Django had any machinery for > request/response processing, middleware, etc., given that what you're > describing is more neatly handled by just writing a WSGI application > and taking advantage of the existing tools. Because WSGI is a horrible API for developers. I'd love to see Django request/response become a simple developer-friendly wrapper around WSGI, provided we gained rather than lost flexibility and power in the process. I'd like to see the distance between a Django application (or a Django view) and WSGI as small as possible. Imagine if you could drop a Django view in to any WSGI container just by applying a WSGI-to- Django-view wrapper of some sort. Or, imagine taking a WSGI application, wrapping it up as a Django view and deploying it straight in to a Django URL configuration. Cheers, Simon --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
