Opened 12 years ago
Closed 11 years ago
#354 closed enhancement (wontfix)
lsapi upstream module
Reported by: | Mahmoud Al-Qudsi | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | nginx-module | Version: | 1.3.x |
Keywords: | lsapi | Cc: | |
uname -a: | |||
nginx -V: | n/a |
Description
This ticket is to feel out the demand/support for an lsapi module in nginx.
LSAPI [0] was developed by LiteSpeed Technologies but is not to be confused with the LiteSpeed webserver itself. LSAPI is a light-weight binary transport to facilitate communication between frontend servers (e.g. nginx) and backend application servers (e.g. PHP or Ruby).
LSAPI hash been shown to be a better-performing option than a highly-tuned FastCGI configuration, all other things being equal; with something around 10-20% improvement over PHP-FPM and 40%+ in the case of Ruby.
The LSAPI protocol code is open source under the BSD-license, and as such there should be no license conflict. Like FastCGI/FPM, LSAPI is now in mainstream PHP as of version 5.3. There are other advantages to LSAPI such as .htaccess support, but they are secondary incentives to the performance metric.
The LSAPI code can be found at [1].
0: http://www.litespeedtech.com/lsapi-litespeed-server-application-programming-interface.html
1: http://www.litespeedtech.com/lsapi-downloads.html
The LSAPI doesn't seems to be a specified protocol, but rather a code which might be considered at most as an ad hoc specification (not sure if there is anything from server part though). This certainly isn't something we want to implement in nginx, at least until some significant benefits are shown.