Henri Gomez wrote:
What about adding/updating of webapps ? Is this a feature that will never be added ( because if it will be and it is not part of the design - then we're back to spaghetti )
Well if you recall my AJP/1.4 proposal it was on my wish-list :
Adding/Removing/Updating a webapp on a tomcat instance is on the features list.
I think it should be done by adding/removing the mapping between Apache and the particular Tomcat instance.
Henri,
My point was that "just apache2+tcp+ajp and nothing else" is not realistic. You can't expect to start with a trivial feature, forwarding
requests - and then be able to grow without pain to support very complex features like add/remove of webapps.
We tried this already.
Major features have a big impact on the code. In this case - if you
want to add/remove/update webapps - you need to implement your own mapper - and the integration with apache ( where location is used ) no
longer works. Or you need to hack apache to support changes to the mapper.
If you want to support cluster reconfiguration - storing the list of cluster servers in httpd.conf may make things harder to save. So you may want to save the properties where you allow changes in a separate file ( htpasswd is an example of apache conf that is not in httpd.conf ). But then you'll have 2 ways to configure something, and more complexity in the code.
Costin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
