tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Henri Gomez <hgo...@apache.org>
Subject Re: Jk2 object model
Date Fri, 09 Jan 2004 09:02:53 GMT
Henri Gomez a écrit :

> Mladen Turk a écrit :
> 
>>  
>>
>>
>>> -----Original Message-----
>>> From: jean-frederic clere Sent: 9. siječanj 2004 8:35
>>> To: Tomcat Developers List
>>> Subject: Re: Jk2 object model
>>>
>>>
>>>>> The concept (approach) as I see it is to be able to make a 
>>>
>>>
>>> connector
>>>
>>>>> (integrator), that would allow the zero-based-configuration. Meaning
>>>>
>>>>
>>>>
>>>> Can we do this by evolving mod_jk or mod_jk2? I don't know. 
>>>
>>>
>>> The other good thing of mod_webapp is to have a good protocol (WARP). 
>>> May be we can reuse it in the new connector.
>>>
>>
>>
>> You see, those are thinks I wish to investigate.
>> JK2 has a good OO model, the JK has simplicity, webapp has a good 
>> protocol,
>> but that doesn't mean that either of them has all that's needed (at least
>> from my perspective).
>>
>> I agree that the 'evolution' is the most pragmatic approach, but again to
>> 'evolutes' from what?
>>
>> If some (or all) codebases will enable to use the TC not only in 
>> webserver,
>> but in the simple console app, that's fine. If we find a way 
>> (extending the
>> AJP protocol thought) to allow zero-based-admin for existing connectors,
>> that's fine too.
>>
>> Something like, will ask for developer support, that if missed will
>> eventually 'stabilize' the project.
> 
> 
> I like this idea of 'integrator', or provider, or broker.
> 
> The term connector is way too limitative, and I'm not sure
> we should restrict it to just a way to make a web server discuss
> with one or many tomcats.
> 
> If we want to do revolution, let's start from this postulat :
> 
> - We want a piece of code which will make tomcats AND outside
>   world communicating. Outside world could be a webserver, but it
>   could be also a cache server, a proprietary application....
> 
> The general idea is to create a Native Tomcat Broker, which could
> be use of course in web servers.
> 
> If we agree on the goal, the model (OO, JMX, APR, WHATEVER++) will follow.
> 
> As many I feel that jk (and maybe also jk2) are now pretty stable,
> and I don't see the need for a new just web/tomcat connector.
> 
> Why ?
> 
> Because, this new connector may fail as failed mod_webapp, because
> we'll create confusion in users mind, 1, 2, 3 connectors to link a web
> server to a tomcat, and rise the usual questions :
> 
> - which connector should be used ?
> 
> - why so many implementation of the same functionnality ?
> 
> 
> And we even a little more ambitious, we could think in term of Java to 
> Native broker, not sure Tomcat to Native...


Good suggestion from one of my co-workers, this kind of broker could be
the native part of ... Coyote ?


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


Mime
View raw message