tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mladen Turk <mt...@apache.org>
Subject Re: JK and AJP protocol enhancements
Date Mon, 10 Jul 2006 09:34:44 GMT
Costin Manolache wrote:
> What's the status with mod_proxy ?
> 
> It seems this kind of change would break backward compatibility, and if 
> this
> happens - maybe it's better to fix the protocol marshalling limitations or
> change it completely.
> I hate the idea of patching an old and mostly broken marshalling model.
>

The point is that it will be backward compatible.
It means that for headers < 8K any current AJP 1.3 protocol
could be used as is.
If there is a larger header, then the current AJP1.3 implementation
will return 'error message' (as now), while the new one will
handle it by requesting additional header packets.
Also if the old 1.3 consumer is in front of the new 1.4 producer
nothing will change.

Resolving 8K header limitation and allowing a single header to be
larger then 33K, while presere the backwards compatibility and it can
be done. It would make receiver and producer a little bit more
complex, but not that much. It would still maintain the zero-copy
failover, that IMHO is the major advantage of AJP protocol, without
the need to prefetch the entire header data.

Regards,
Mladen

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message