On 3/16/06, Dave Newton <[EMAIL PROTECTED]> wrote: > Frank W. Zammetti wrote: > > > Unfortunately, it has one minor drawback: it doesn't work :) > > > > Minor quibble. > > Dave
Frank, Dave... even if it would work, how can you guarantee it resolves the proper hostname? the default linux installation resolves InetAdress.getLocalhost() to "localhost" until you remove the 127.0.0.1 line from your etc/hosts. Whats with vhosts? If the "master" simply make connections to the slave, that any master-accessible url is ok, but if the master sends the user a redirect to the slave, then knowing the outer address is important. Speaking about crazy solutions... what you actually could do would be opening a socket to the master, let the master send your incoming requests via this connection, fake the container, creating your own HttpServlerRequest/Response objects, send the reply over the same connection. This would be fun to implement, but you'll be in no need for the container (and the master will need a lot of synch and threadpools). thinking further, you don't need to fake anything, you could define your own connector in tomcat config and let him connect to the master and maintain the connection for incoming requests. I'm not quite sure whether you can easily switch connectors under tomcat or whatever jsp engine you are using, but it can be patched :-) However, once you leave the company for a better job, they will have to rewrite the complete load balancing or hire someone with good research skills, to find this threat und understand the design decision :-) regards Leon --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
