Opened 16 years ago

Closed 13 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 by mramm, 16 years ago

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 by mramm, 16 years ago

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 by anonymous, 16 years ago

Cc: andy@… added

comment:4 by (none), 15 years ago

milestone: post-1.0

Milestone post-1.0 deleted

comment:5 by Jacob, 15 years ago

Triage Stage: UnreviewedAccepted

comment:6 by anonymous, 15 years ago

Cc: dane.springmeyer@… added

comment:7 by Thejaswi Puthraya, 15 years ago

Component: UncategorizedHTTP handling

comment:8 by Luke Plant, 13 years ago

Severity: Normal
Type: New feature

comment:9 by Luke Plant, 13 years ago

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