Costin Manolache wrote:
+1 on removing from trunk.
IMHO AJP as a protocol is a dead end - it is not worth extending,
Agreed. It has to many limitations to satisfy the
modern webserver/backend connector.
and certainly not
worth creating a new protocol. We need to pick one of
thrift/protobuf/hessian for
marshaling, and start doing some mux-ing in the protocol.
All those framework you mention are just helpers for
*building* the custom protocol. They actually mandate
that we will have one but now hidden inside some IDL
language description. Any such framework makes
almost impossible to change the protocol specification
while preserving backward compatibility
(One huge problem why AJP is not usable any more)
I'm kind of more fun of
http://www.wsgi.org/wsgi/
At least it's human readable and already working :)
Regards
--
^(TM)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
