Differences between revisions 37 and 39 (spanning 2 versions)
Revision 37 as of 2006-05-30 19:36:02
Size: 4791
Editor: 193
Comment:
Revision 39 as of 2006-08-03 08:32:19
Size: 4783
Editor: LAubervilliers-151-11-55-32
Comment: revert to previous version
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
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. 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 11: Line 11:
 * [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. See [http://svn.eby-sarna.com/wsgiref wsgiref] for source code.)  * [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. See [http://svn.eby-sarna.com/wsgiref wsgiref] for source code.)
Line 33: Line 33:
 * [http://peak.telecommunity.com/ Peak] has CGI and FastCGI gateway and server  options [http://mail.python.org/pipermail/web-sig/2004-October/000966.html more info]  * [http://peak.telecommunity.com/ Peak] has CGI and FastCGI gateway and server options [http://mail.python.org/pipermail/web-sig/2004-October/000966.html more info]
Line 49: Line 49:
 * [http://pythonpaste.org/wareweb/ Wareweb] - a rethinking of Webware/WebKit   * [http://pythonpaste.org/wareweb/ Wareweb] - a rethinking of Webware/WebKit
Line 65: Line 65:
 * [http://www.zope.org Zope]  Zope 3 is now a WSGI application.  It ships with the Twisted   * [http://www.zope.org Zope] Zope 3 is now a WSGI application. It ships with the Twisted

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.

See [http://www.python.org/peps/pep-0333.html PEP 333] for more information on WSGI.

Web Server implementations

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.