I'm not sure I'm following your here.
Why exactly mod_tora for lighty or nginx cannot connect directly to
the tora host and use the protocol as mod_tora for Apache is doing ?
I maybe have a wrong vision of tora.
You may have think mod_tora "only" as a http server plugin to solve some
memory comsumption issues.
But for me, programmer and sysadmin (can't choose only one, both are
madly enjoying ), tora must be a scalable way to deploy neko
application in web farms, so the lighttpd/nginx/... implementation
should be able to connect to several tora instances, load balance and
failover between them, like it's done with fastcgi on lighttpd and nginx.
I can understand that, but IMHO that's just a matter of configuration.
Once the tora server is selected (depending on balancing and failover),
you should be able to use tora protocol.
Or am I missing something else ?
The proxy paradigm make difficult to implement the tora multipart
content scheme, be able to pass raw data to tora without have to wait
for the CGetMultipart code would be a lot easier to implement in
lighttpd, and seems to be required for nginx (
http://marc.info/?l=nginx&m=121425082522327&w=2 )
Yes, this is similar to what mod_tora is doing, for similar reasons I
guess, which are the necessity to stream multipart/POST data only when
requested to do so.
I'm not sure however what exactly a nginx/lighty "proxy" (between?) is
doing here so you might have to explain it to me first :)
It might be possible to modify the tora protocol to let the server parse
and send the multipart data without waiting for the CGetMultipart : this
should not actually interfere with the client since it's not expecting
anything else from the server.
Nicolas
--
Neko : One VM to run them all
(http://nekovm.org)
