Opened 14 years ago

Closed 11 years ago

#8928 closed New feature (duplicate)

Make a WSGI compatibility layer for Django middleware

Reported by: simon Owned by: nobody
Component: HTTP handling Version: 1.0
Severity: Normal Keywords:
Cc: andy@…, dane.springmeyer@… Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


Another Mark Ramm suggestion at DjangoCon.

Change History (9)

comment:1 Changed 14 years ago by mramm

The idea here is that there should be easy access to a wsgi environ like dictionary, to make calling wsgi applications from within django trivial.

I would even propose that making a call_wsgi_app function that grabs the environ, creates a start_response callable, calls the wsgi app, and returns the response properly.

This would let users write code like:

def someview(request, *args)
    return call_wsgi_app(wsgi_app, request)

This would allow people who use django with SQLAlchemy to user RUM (A django admin like wsgi app) from a veiw, or to use some SOAP wsgi application, or a TurboGears app, or whatever they want in a Django view.

comment:2 Changed 14 years ago by mramm

Ok, previous comment was meant for ticket 8927.

In this case, it would be awesome if the distinction between django middleware and wsgi middleware could mostly go away.

comment:3 Changed 14 years ago by anonymous

Cc: andy@… added

comment:4 Changed 13 years ago by (none)

milestone: post-1.0

Milestone post-1.0 deleted

comment:5 Changed 13 years ago by Jacob

Triage Stage: UnreviewedAccepted

comment:6 Changed 13 years ago by anonymous

Cc: dane.springmeyer@… added

comment:7 Changed 13 years ago by Thejaswi Puthraya

Component: UncategorizedHTTP handling

comment:8 Changed 11 years ago by Luke Plant

Severity: Normal
Type: New feature

comment:9 Changed 11 years ago by Luke Plant

Easy pickings: unset
Resolution: duplicate
Status: newclosed

This appears to be a dupe of #8927.

Note: See TracTickets for help on using tickets.
Back to Top