ServerJS/WSGI: Difference between revisions
< ServerJS
Jump to navigation
Jump to search
(New page: = Web server to application interface = A well-defined interface for connecting web applications to web servers is a very powerful thing. This approach has enabled applications written wi...) |
|||
| Line 12: | Line 12: | ||
== Proposed API == | == Proposed API == | ||
Proposal for JSGI specification: http://jackjs.org/jsgi-spec.html | |||
== Related Discussions == | == Related Discussions == | ||
* [http://groups.google.com/group/serverjs/browse_thread/thread/43372363c819859b "Obviously stupid JS WSGI gateway"] | * [http://groups.google.com/group/serverjs/browse_thread/thread/43372363c819859b "Obviously stupid JS WSGI gateway"] | ||
Revision as of 19:38, 2 June 2009
Web server to application interface
A well-defined interface for connecting web applications to web servers is a very powerful thing. This approach has enabled applications written with any Java framework, for example, to be deployed behind and Java server ("servlet container"). Additionally, the standard interface allows the creation of "middleware", or software that sits in between the server and the application. There are many useful applications for middleware (automatic application of site wide styling, caching and sessions, security).
Prior Art
- Web Server Gateway Interface (Python). Very successful interface, but experience has shown that it's not 100% ideal.
- Ruby Rack. An up and coming standard in Ruby that looks a lot like WSGI 2.0.
- Java Servlets. One of the first language-specific interfaces.
- The Jack project provides a WSGI/Rack-like standard interface to webservers in JavaScript: http://jackjs.org
Proposed API
Proposal for JSGI specification: http://jackjs.org/jsgi-spec.html