Hiya, thanks for replying. I'm not really sure what you mean though!
By AJP13 do you mean http://tomcat.apache.org/connectors-doc-archive/jk2/common/AJPv13.html?
I don't want to use servlets or the servlet SDK, and I don't want to
pass filesystem references to big files back to the webserver. I want
to write simple, task-specific mainly POJO java applications which
carry out one job upstream of the front-end webserver, and can speak
FastCGI protocol to that webserver, without having to use a J2EE/JSDK
layer. How does the X-Sendfile relate to this? Perhaps I'm missing
something important, please let me know!
Thanks,
Igor
On 14 Apr 2008, at 16:11, Mathieu Lecarme wrote:
Igor Clark a écrit :
Hi Daniel,
This sounds great. My interest in FastCGI and Mina is to implement
a sort of application-server "layer" with which one can quickly
develop very domain-specific server components (e.g. image
generator, feed aggregator, etc) without needing to use a big fat
J2EE back-end or a PHP everything-but-the-kitchen-sink application
server/scripting engine.
Don't forget the lighty's X-Sendfile. With this header, mina can do
something like ACL, logging, cache check, and give the hand back to
httpd to serve some files.
FastCGI is just a standard ajp13.
M.
