Search results
Results From The WOW.Com Content Network
The Web Server Gateway Interface (WSGI, pronounced whiskey [1] [2] or WIZ-ghee [3]) is a simple calling convention for web servers to forward requests to web applications or frameworks written in the Python programming language. The current version of WSGI, version 1.0.1, is specified in Python Enhancement Proposal (PEP) 3333. [4]
Web Server Gateway Interface (WSGI) is a modern approach written in the Python programming language. It is defined by PEP 3333 [ 10 ] and implemented via various methods like mod_wsgi (Apache module), Gunicorn web server (in between of Nginx & Scripts/Frameworks like Django), UWSGI , etc.
It is built as a successor to the Web Server Gateway Interface (WSGI). Where WSGI provided a standard for synchronous Python application, ASGI provides one for both asynchronous and synchronous applications, with a WSGI backwards-compatibility implementation and multiple servers and application frameworks.
uWSGI is an open source software application that "aims at developing a full stack for building hosting services". [3] It is named after the Web Server Gateway Interface (WSGI), which was the first plugin supported by the project.
Django can be run in conjunction with Apache, Nginx using WSGI, Gunicorn, or Cherokee using flup (a Python module). [25] [26] Django also includes the ability to launch a FastCGI server, enabling use behind any web server which supports FastCGI, such as Lighttpd or Hiawatha. It is also possible to use other WSGI-compliant web servers. [27]
The WSGI standard is an interface that allows applications to use Python code to handle HTTP requests. A WSGI application is passed a Python representation of an HTTP request by an application, and returns content which will normally eventually be rendered by a web browser.
The Gunicorn "Green Unicorn" (pronounced jee-unicorn or gun-i-corn) [2] is a Python Web Server Gateway Interface (WSGI) HTTP server. It is a pre-fork worker model, ported from Ruby's Unicorn project. The Gunicorn server is broadly compatible with a number of web frameworks, simply implemented, light on server resources and fairly fast. [3]
CherryPy tools hook into events within the request process. Whenever the CherryPy server receives a request, there is a specific set of steps it goes through to handle that request. Page handlers are only one step in the process. Tools also provide a syntax and configuration API for turning them on and off for a specific set of handlers.