![]() |
Lsapi api
I seem to recall that the original intent for LSAPI is that it would be an alternative to the fastcgi protocol.
How is this effort going? Will LSAPI be documented and available for use for our own executable programs? It seem this has stalled and that's a shame, I'm sure people are interested in this. |
lsapi has been there for years. and every release include them: for php and ror.
here's php lsapi document: http://www.litespeedtech.com/php-litespeed-sapi.html We did benchmark recently, here's the detail of lsapi vs fastcgi: http://blog.litespeedtech.com/2010/0...ginx/#more-173 |
you misunderstood the question.
You publish PHP-LSAPI and Ruby-LSAPI. We all know that. However, you guys said that you would publish the API for LSAPI so that we could use it for our own applications. E.g. for things other than PHP and Ruby. This was mentioned long ago as a goal. I see no movement in this goal. Do you now understand what I am asking about? |
You can use our PHP-LSAPI and Ruby-LSAPI code as an example. All client side code is open, the API is pretty much like FCGI, we can provide a simple sample code like the "echo" FCGI example.
We do not spend much time to push it as an third party integration API as there is not much interest in it even though the code is completely open, pretty much all are internal development. |
yeah, I knew I could dig around the php-lsapi code.
I think there "is not much interest" because it has never been published and documented. If somebody spent the time to properly document the API, then people would consider using it. Given the benchmarks that nitewave just linked to, why would people not be interested in using it over fastcgi? Certainly if they are already litespeed clients, but perhaps promoting LSAPI for any application might result in new ones. It's a distinguishing feature that sets litespeed apart. I personally think it would be worth litespeedstech's time to document it properly. I wouldn't think it would change much, so it should be a minimal effort to maintain once it was written. If it turns out nobody cares, it didn't cost much (a few hours time?), and it could potentially be very interesting to prospective clients. |
By the way, had this already been published, maybe somebody would have created and shared the python and mono LSAPI interfaces by now. Per your own reference:
http://www.litespeedtech.com/support...ead.php?t=1883 That was 12 releases ago, right? Document the interface, and maybe the community will come up with these and more, faster. |
I'd certainly be interested in porting some fcgi Python applications over to LSAPI, in addition to my fcgi C++ apps.
|
LSAPI is pretty much like FCGI API, below is a simple example, which is like FCGI echo example, it shows you how to access request header, request body, create its own listener socket, etc. Just link it with lsapilib.c .
All the API functions are in lsapilib.h, it is easy to figure out what a function does from the function name. And code is open, it should be easy to figure out any thing. Code:
#include <lsapilib.h> |
Okay, thanks.
I may use LSAPI with Ada. If I am able to do so cleanly, I'll publish the code and maybe some documentation. No promises, and it's not immediately on my list of things to do. |
| All times are GMT -7. The time now is 04:23 AM. |