I can't answer all your questions, but I hope I can 
shed some light on some questions:

The connectors consists typically of two parts:
- a C part for apache/iis/..
- a java part for tomcat.

These parts communicate with each other through some 
means that are specific to the connector.
The common way to communicate between the parts
is to talk over a socket.
- mod_wepapp with WARP
- mod_jk/mod_jk2 with AJP 

In this case you have something like
         
[process-1:apache->mod_jk]->Socket->[AjpConnector->tomcat:process-2]

So 'both sides' means both parts of the connector 
('the modules on both sides of the socket'.)
The binary part is the apache module.

So parts can be treated independly, as long as both side 
talk the same protokoll.

In adition to this there are other ways to communicate
- mod_jk/mod_jk2 has an interface for inprocess communication
  That's the reason why there are some setup parameters
  in the jk property files, that confuse the people (like 
  java_home etc.)

>From what I see there is something like a wave development.

Sometimes both parts of the connector are treated as one 
project, sometimes as two projects. The second happens as 
long, as the developers implement against a well defined 
protocol, but as soon as they start to change the protocoll
or implement an additional protocol they merge. (Otherwise 
you won't have a partner to talk to).

Ralph Einfeldt
Uptime Internet Solution Center GmbH
Hamburg, Germany
Hosting, Content Management, Java Consulting
http://www.uptime-isc.de 

> -----Urspr�ngliche Nachricht-----
> Von: Turner, John [mailto:[EMAIL PROTECTED]]
> Gesendet: Donnerstag, 26. September 2002 14:57
> An: 'Tomcat Users List'
> Betreff: RE: AW: Copious Connectors Conundrum
> 
> What does "both sides" mean?  What does each "side" 
> do exactly?  Are the connectors now part of the Tomcat 
> project, or are they still off on their own?  What did 
> you mean that the "binary side" is considered "beta"?
> What is the "binary side"?

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to