Graham Leggett wrote: > > Henri Gomez wrote: > > > 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. > > An URL is a logical solution, which leaves us with two choices: > > - A specific out-of-band URL predefined in httpd where httpd > is told "get your config regularly here". This URL could be > served by tomcat, or any other server. > > - In-band hop-by-hop header information that is deployed with > responses from the backend servers. This has the advantage of > having httpd learn about the status of backends on an up to > the minute basis on each hit. > httpd will already use certain in-band info, like whether a > request was > successful or not, or how long the request took. > > I prefer the in-band approach, as it's consistent. As has > been pointed out, BEA Weblogic does this with success, so > admins out there will not find this a foreign concept. >
+1 for X-Headers. Any other solution is IMO either too complicated at the moment or inadequate. We are already parsing headers from the backend so the information is inherently already there. All that is needed is to reed it, and update configuration accordingly. MT.
smime.p7s
Description: S/MIME cryptographic signature
