Django

Code

Ticket #8928 (new)

Opened 2 years ago

Last modified 10 months ago

Make a WSGI compatibility layer for Django middleware

Reported by: simon Assigned to: nobody
Milestone: Component: HTTP handling
Version: 1.0 Keywords:
Cc: andy@andybak.net, dane.springmeyer@gmail.com Triage Stage: Accepted
Has patch: 0 Needs documentation: 0
Needs tests: 0 Patch needs improvement: 0

Description

Another Mark Ramm suggestion at DjangoCon.

Attachments

Change History

09/07/08 14:19:29 changed by mramm

  • needs_better_patch changed.
  • needs_tests changed.
  • needs_docs changed.

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)
    do_something(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.

09/07/08 14:23:10 changed 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.

10/04/08 18:58:46 changed by anonymous

  • cc set to andy@andybak.net.

02/25/09 13:51:44 changed by

  • milestone deleted.

Milestone post-1.0 deleted

02/25/09 16:35:12 changed by jacob

  • stage changed from Unreviewed to Accepted.

03/20/09 01:24:31 changed by anonymous

  • cc changed from andy@andybak.net to andy@andybak.net, dane.springmeyer@gmail.com.

05/08/09 11:09:38 changed by thejaswi_puthraya

  • component changed from Uncategorized to HTTP handling.

Add/Change #8928 (Make a WSGI compatibility layer for Django middleware)




Change Properties
Action