I recently wrote a basic web service, and I am writing a client app consume
it. Here's the trick - I want the client to be able to request the web
service without knowing exactly where it is. Specifically I want the client
to send a request on the local network, and have the web service respond
with it's location. For instance, I might have the web service on
"WebServer1". The client would send out a request on the local network, and
the web service would respond with it's location (in this instance
WebServer1). If, later, I moved the web service to WebServer2, the client
would be able to locate it by sending another request. The client would
then consume the web service. Is there a way to do this? Or does the
client always have to know in advance where the web service is located in
order to use it?
Thanks,
Michael C
DalePres - 08 Feb 2005 04:32 GMT
Check out UDDI at http://uddi.microsoft.com/. You can also put a UDDI
server on your own network.
HTH
DalePres
MCAD, MCDBA, MCSE
>I recently wrote a basic web service, and I am writing a client app consume
>it. Here's the trick - I want the client to be able to request the web
[quoted text clipped - 11 lines]
> Thanks,
> Michael C
Michael C# - 08 Feb 2005 14:58 GMT
Thanks DalePres. I'm trying to figure out the best way to package and
distribute a web service. I suppose if you're asking a client to install
and configure IIS on their local network, you might as well ask them to go
the extra step and install/configure a UDDI server as well. It seems Web
Services are designed to be easier to access from pre-configured centralized
global repositories. I guess for local stuff I need to find a more
localized solution.
Thanks,
Michael C
> Check out UDDI at http://uddi.microsoft.com/. You can also put a UDDI
> server on your own network.
[quoted text clipped - 19 lines]
>> Thanks,
>> Michael C