It would be nice if Cherokee was to support the AJPv13 or later, so that it can act transparently with Apache Tomcat.

Some options aren't handled correctly by using a Forward/Reverse Proxy approach, which isn't enough. For example, trying in Tomcat to determine the real IP of the incoming connection. Moreover, the AJP protocol should allow faster serving of pages.

As a reference, see http://tomcat.apache.org/connectors-doc/ajp/ajpv13a.html; the native Apache's mod_jk is the one which needs porting.

Hi, I thought Alvaro said last night it was an old method to connect to it... so unless someone really wants to write it, I wouldn't count on this connector soon.

Cloud someone please explain to me some advantage of using AJP over HTTP? Last time I checked GlassFish (I think it was GlassFish, I'm not sure though) it didn't even supported AJP by default..

The theoretical performance improvement is something that somebody ought to check. (I doubt there will be any
perceptible performance different, actually).

There are several blog entries about Glassfish and AJP (mod_jk). This is from one of the architects in the Glassfish team:

http://weblogs.java.net/blog/jfarcand/archive/2006/03/running_glassfi_1.html

Some arguments for AJP from this page: http://tomcat.apache.org/connectors-doc/ajp/ajpv13a.html

• Increasing performance (speed, specifically).
• Adding support for SSL, so that isSecure() and getScheme() will function correctly within the servlet container. The client certificates and cipher suite will be available to servlets as request attributes.

Another advantage of AJP over a simple reverse proxy implementation is that web applications that embed self-referential URLs in their responses will return the correct hostname & port number whereas with a simple proxy the application needs special knowledge of the proxy host to return the right URL and this likely won't be possible if you don't have the source code...