Thus, simplicity of implementation on both the server and framework Investment in the interface can be reasonably low. Thus, WSGI must be easy to implement, so that an author’s initial Is little immediate reward for an author who implements WSGI support. However, since no existing servers or frameworks support WSGI, there Server and framework authors and maintainers must actually implement Web servers and web applications or frameworks: the Python Web Serverīut the mere existence of a WSGI spec does nothing to address theĮxisting state of servers and frameworks for Python web applications. This PEP, therefore, proposes a simple and universal interface between That suits them, while freeing framework and server developers toįocus on their preferred area of specialization. CGI, FastCGI, etc.) – would separate choice ofįramework from choice of web server, freeing users to choose a pairing mod_python), or invoke Python via a gateway Python – whether those servers are written in Python (e.g. The availability and widespread use of such an API in web servers for Written with any Java web application framework to run in any web This wide variety of choices can be a problemįor new Python users, because generally speaking, their choice of webįramework will limit their choice of usable web servers, and viceīy contrast, although Java has just as many web application frameworksĪvailable, Java’s “servlet” API makes it possible for applications Such as Zope, Quixote, Webware, SkunkWeb, PSO, and Twisted Web – to Python currently boasts a wide variety of web application frameworks, Original Rationale and Goals (from PEP 333) Servers and Python web applications or frameworks, to promote webĪpplication portability across a variety of web servers. This document specifies a proposed standard interface between web You may view its SVN revision history, from revision 84854 forward. Rules outlined in the sections below titled, A Note On Stringįor detailed, line-by-line diffs between this document and PEP 333, Under Python 3, however, your app or server must also follow the Is compliant to PEP 333, it is also compliant with this PEP. While for procedural reasons, this must be a distinct PEP, noĬhanges were made that invalidate previously-compliant servers orĪpplications under Python 2.x. Usability under Python 3, and to incorporate several long-standingĭe facto amendments to the WSGI protocol. This is an updated version of PEP 333, modified slightly to improve Optional Platform-Specific File Handling.Supporting Older (Middleware Handling of Block Boundaries.Middleware: Components that Play Both Sides.Original Rationale and Goals (from PEP 333).Eby Discussions-To : Web-SIG list Status : Final Type : Informational Created : 2 Post-History : 2, 0 Replaces : 333 Toggle light / dark / auto colour theme PEP 3333 – Python Web Server Gateway Interface v1.0.1 Author : P.J. PEP 3333 – Python Web Server Gateway Interface v1.0.1 | Following system colour scheme Selected dark colour scheme Selected light colour scheme Python Enhancement Proposals
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |