On 8 Nov 2005, at 08:47, Ian Bicking wrote:
However, I don't think you'd lose anything by routing everything
through
WSGI.
IIRC, the reason Django doesn't use WSGI in the first place is that
when we first created it two years ago WSGI was still being fleshed
out on the Python Web SIG mailing list. Django's HttpRequest and
HttpResponse classes were designed to solve pretty much the same
problem as WSGI - we didn't want to code against the mod_python API
(in case it turned out not to be stable/scalable enough for our
needs) so we created our own abstraction layer to let us easily
switch hosting platforms if we needed to.
That said, I personally find the Django class interfaces "fit my
brain" a lot better than WSGI does - but I can't see any reason not
to use WSGI underneath and just use a single WSGI-to-Django mapping
layer (which we already have in the WSGI handler). It would reduce
the amount of code we would have to maintain.
Cheers,
Simon
