Graham Leggett wrote:
Costin Manolache wrote:
Httpd already has some support for that - .htaccess for example
The trouble with .htaccess is that it only applies for data on the local filesystem. Url space created by other content handlers (such as proxy or ajp) is not covered.
You're assuming that the tomcat admin has access to this config file, which is often not going to be the case. If you have to update a file on the httpd server, it's virtually no different to updating a file on the httpd server and issuing a graceful restart, and we already have that now.
Well, this is an excelent point that I forgot to make :-)
Yes, one of the most important benefits of having this dynamic config is that you _don't_ need direct access and editing of the httpd.conf. If the data about the cluster is by default stored in a file ( and without the Include tricks ), then it becomes possible to have the changes made using some program - either as a result of negotiation and tomcat JMX pushing new settings, or using config scripts, etc.
You keep coming back to "stored in a file". This file is stored where? On the httpd server? On the tomcat server?
If it's on the httpd server, then you're back to editing a file on the webserver, and here there is no point - if you're already on the httpd server editing files, then you already probably have the power to issue a graceful restart anyway, which reloads the httpd service gracefully without breaking connections or otherwise inconveniencing users.
If it's on the tomcat server, then how does httpd access the file? In band using either http or ajp? Out of band using SMB or NFS?
Then there is the issue of securing that file - obviously you don't want just anybody accessing it or changing it.
And then what if the httpd server is an appliance such as an SSL accelerator? No chance for a file there.
Well using an URL could be a good idea, since it could be :
- a static file, edited by admin, on the web-server or another web-server/tomcat
- a dynamically generated file, PHP/JSP/Servlet/PERL, whatever.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
