> 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.
Right now the port was the problem. We are not using name-based virtual hosts and IP would be sufficient. And it's easy to get from request by the master server when slave is calling http://my-master:8080/master-app/register-slave.do. > 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 :-) Another reason for such architecture was ease and speed of development. Most of actions (for example associated with configuration) called by master-server are also available from slave's admin console. So when we implement one receiver for either master call or web admin form then we have receiver for the other. > 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 :-) Blah, there are a lot of _interesting_ design and architecture decisions in this company. It's called innovative :D Wojtek --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
