You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by jean-frederic clere <jf...@fujitsu-siemens.com> on 2001/06/15 21:33:55 UTC
structure for Tomcat-Connectors
Hi,
I am trying to think about a structure for our connectors:
From httpd From httpd
| |
+++++++++++++++++++++++++++++++++++++++++++++++++ |
+ AP1.3 | AP2.0 | NETSCAPE | DOMINO | others | |
+++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++
+ core mod_jk + + mod_backhand +
+++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++
+ ajp12 | ajp13 | apj14 | warp | new protocols + |
+++++++++++++++++++++++++++++++++++++++++++++++++ |
| |
To JVM To JVM
| |
+++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++
+ ajp12 | ajp13 | apj14 | warp | new protocols + + HTTP +
+++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++
+ Tomcat layers + + +
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ .......... +
That would means that if we are writting a warp connector we should only be
worried by the protocol and have 2 sets of routines one to get/send information
from/to a core module, one to send/get information to/from a Tomcat.
In a configuration like that the Apache 2.0 specialist would write the AP2.0
part, the Apache1-3 the AP1.3 and so on.
Having a defined interface to Tomcat there should be not problem to get a
protocol supported by all Tomcat versions.
* mod_backhand is not (yet) ours.
Any comments?
Nice week-end
Jean-frederic