WSGI

From Wikipedia, the free encyclopedia

The Web Server Gateway Interface defines a simple and universal interface between web servers and web applications or frameworks for the Python programming language.

Contents 1 Idea 2 Specification overview 3 Example application 4 WSGI-compatible applications and frameworks 5 Wrappers 6 External links

[edit] Idea

Python boasts a wide variety of web application frameworks. This can be a problem for new Python users because, generally speaking, their choice of web framework will limit their choice of usable web servers, and vice versa.

WSGI proposes a simple and universal interface between web servers and web applications or frameworks.

[edit] Specification overview

The WSGI interface has two sides: the "server" or "gateway" side, and the "application" or "framework" side. The server side invokes a callable object that is provided by the application side. Additionally WSGI provides middlewares, components that play both sides.

A "middleware" component can perform such functions as:

• Routing a request to different application objects based on the target URL, after rewriting the environ accordingly.
• Allowing multiple applications or frameworks to run side-by-side in the same process
• Load balancing and remote processing, by forwarding requests and responses over a network
• Perform content postprocessing, such as applying XSL stylesheets

[edit] Example application

A WSGI compatible "Hello World" application:

def app(environ, start_response):
    start_response('200 OK', [('Content-Type', 'text/plain')])
    return ['Hello World\n']

[edit] WSGI-compatible applications and frameworks

There are numerous Web application frameworks supporting WSGI:

• Django
• TurboGears
• Pylons

Additionally there are two simple publishers:

• flup
• Colubrid

[edit] Wrappers

The server or gateway invokes the application callable once for each request it receives from an HTTP client, that is directed at the application.

Currently wrappers are available for FastCGI, CGI, SCGI, AJP using the flup package.

[edit] External links

• PEP 333 defining the interface standard
• http://www.pythonpaste.org/ - WSGI metaframework
• http://www.saddi.com/software/flup/ - Flup Publisher and Request Handlers