On 11/30/07, Simon Willison <[EMAIL PROTECTED]> wrote: > It's probably too big a feature to start talking about now, but I'd be > really interested in seeing Django applications (in particular the > URLconf part) unified with the concept of a Django view, so a Django > application is a callable that takes a request object and returns a > response - and in fact an entire Django deployment can be boiled down > to that. This has a number of advantages:
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. I'd much prefer to have our WSGI issues straightened out so that Django can be a first-class WSGI citizen, and leave dispatch and request/response within the framework as they are. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
