Differences between revisions 4 and 7 (spanning 3 versions)
Revision 4 as of 2004-09-08 21:19:34
Size: 334
Editor: cache6-popl
Comment:
Revision 7 as of 2004-11-06 22:44:17
Size: 1704
Editor: user04
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
Implementations of the Web Server Gateway Interface: = Implementations of the Web Server Gateway Interface =

Note: many of these implementations may be partial/incomplete or noncompliant as of the current draft spec. If you can't get the code samples in the spec to work with one of these implementations, there's a good chance that the implementation is broken: contact the implementation's author.
Line 7: Line 9:
 * None yet AFAIK  * [http://mail.python.org/pipermail/web-sig/2004-October/000956.html wsgiref] - a library of base classes covering most of the "hard parts" of a WSGI server implementation, written by the PEP author. It also includes utility functions and classes that may be useful for application/framework implementors, and should be considered a "must read" for server implementors. (Update: most of the limitations mentioned in the linked post have now been resolved; wsgiref now includes sensible default error handling and logging, automatic calculation of Content-Length when possible, and greater test coverage.)

 * [http://www.xhaus.com/modjy modjy] - a WSGI implementation for Jython

 * see Jonpy below

 * see WSGIUtils below
Line 11: Line 19:
 * [http://mail.python.org/pipermail/web-sig/2004-October/000929.html WSGI for Webware] (work in progress)
Line 12: Line 22:
 * Nevow - in a branch of its Subversion repository.
 * Nevow - in a branch of its Subversion repository. (Can someone supply a link to this?)

 * [http://www.owlfish.com/software/wsgiutils/ WSGIUtils] - A multi-threaded WSGI server implementation and a simple framework providing basic user authentication, signed cookies, and persistent sessions.

Implementations of the Web Server Gateway Interface

Note: many of these implementations may be partial/incomplete or noncompliant as of the current draft spec. If you can't get the code samples in the spec to work with one of these implementations, there's a good chance that the implementation is broken: contact the implementation's author.

Web Server implementations

  • [http://mail.python.org/pipermail/web-sig/2004-October/000956.html wsgiref] - a library of base classes covering most of the "hard parts" of a WSGI server implementation, written by the PEP author. It also includes utility functions and classes that may be useful for application/framework implementors, and should be considered a "must read" for server implementors. (Update: most of the limitations mentioned in the linked post have now been resolved; wsgiref now includes sensible default error handling and logging, automatic calculation of Content-Length when possible, and greater test coverage.)

  • [http://www.xhaus.com/modjy modjy] - a WSGI implementation for Jython

  • see Jonpy below
  • see WSGIUtils below

Web Framework implementations

WSGIImplementations (last edited 2011-01-18 16:31:13 by 89-105-112-41)

Unable to edit the page? See the FrontPage for instructions.