ServerJS/WSGI: Difference between revisions
< ServerJS
Jump to navigation
Jump to search
No edit summary |
|||
| (2 intermediate revisions by the same user not shown) | |||
| Line 9: | Line 9: | ||
* [http://en.wikipedia.org/wiki/Java_Servlet Java Servlets]. One of the first language-specific interfaces. | * [http://en.wikipedia.org/wiki/Java_Servlet 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 | * The Jack project provides a WSGI/Rack-like standard interface to webservers in JavaScript: http://jackjs.org | ||
* Comparison of current WebServer APIs used by JS engines: | |||
**[http://spreadsheets.google.com/pub?key=rMWeXQ2LvhKWqQQ_zEdb8aQ&single=true&gid=0&output=html HTTP incoming request JS APIs] | |||
== Proposed API == | == Proposed API == | ||
Latest revision as of 13:23, 26 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
- Comparison of current WebServer APIs used by JS engines:
Proposed API
Proposal for JSGI specification: http://jackjs.org/jsgi-spec.html