tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Costin Manolache <>
Subject Re: Status/Authority of AJP/1.5
Date Tue, 25 Oct 2005 01:31:26 GMT
I see. Sorry, I've been sleeping for quite a while, I'm slowly getting
up to speed with the latest developments.

Are you saying that mod_proxy_ajp is significantly faster than
mod_proxy ? That's interesting.

To answer your question - ajp10 and ajp11 were used in JServ,
developed in Apache.
Ajp12 is based on 11, developed in the early days of tomcat. I think
jetty also suppors ( or supported ) the protocol at some time.

IMHO - if a new version of the protocol is developed, there are 2 choices:
- preserve backwards compatibility - there are few ugly way to do this
- break backwards compatibility - in wich case it may be better to
redo the protocol so it is extensible, and maybe even better reuse an
existing protocol. An example to look at is the DBUS protocol ( from
freedesktop ) - or maybe classical RPC. Ad-hoc arbitrary binary
protocols can be a bad idea - as we see with ajp12 extensibility


On 10/24/05, William A. Rowe, Jr. <> wrote:
> Costin Manolache wrote:
> > I tought some time ago AJP was 'deprecated' - to be replaced with
> > plain HTTP and mod_proxy ?
> Why?
> It turns out that mod_proxy_ajp v.s. mod_proxy_http does prove the validity
> of optimizing the backend connection.  I don't think anyone forsees mod_jk
> being deprecated (at least, not insofar as it supports IIS/Netscape/Sun
> http servers), but from an Apache perspective, hopefully mod_proxy_ajp will
> make mod_jk/Apache a footnote in history :)
> Bill
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message