On Fri, 28 Jan 2005 08:21:40 -0800, Dakota Jack <[EMAIL PROTECTED]> wrote: > I am not sure at this point David S. what you have tried, but I can > assure you that your conclusion that "configuration is the only way in > this scenario above" is incorrect, because I do this all the time with > no difficulties whatsoever.
How many different host/port combinations are the applications you use this strategy in deployed to? In the environment I "live", apps deploy on multiple servers (always 2+ for high availability), and are likely to be accessed by a different (non-standard) port for each instance. How can you, given that criteria, construct a URL that will work? > The firewall issue is different. It is true that if you have the > correct URL or IP address that a caller cannot get through if there is > a firewall blocking the port. But that is a totally separate concern. > It in fact does make sense to assume that a web service installed on > a network will be reachable from an external network. There would > otherwise be no sense at all to having the web service. If you toss > in these firewall issues, you will only be muddying the waters with > irrelevant concerns that are unrelated to this problem. I disagree. It can make a huge amount of sense to have a web service that exists only behind a firewall. You just haven't seen the usefulness of it yet ... > I hope that did not sound too preachy. I guess I am just pretty sure > in this area and hope that you all will see I am only trying to help. > I am sure because I have gone through all the problems in one way or > another related to this many times. > > Wasn't Martin the originator of this thread? Maybe you are talking > about a sub-thread issue? > > Jack -- Eddie Bush --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
