RE: WSDL Import/Include Locations

Yaron

i was moved by your passion for this subject, and so have been thinking 
a bit more about the load-balancing of WSDL. i now think this is less of
a generic problem with URIs and more of a specific problem with HTTP.
I'd suggest that a 'little-guy' could publish the WSDL and any imported/
included documents not as http:// but under some other more P2P like 
scheme which could implement the balancing to an array of resources
available over HTTP or whatever. Unfortunately such an interoperable
load-balancing transport doesn't exist now, but i don't think that's 
the fault of WSDL, or a problem to be solved in WSDL 2.0.

As for the big-guy, little-guy argument you mentioned in last night's call,
i'm slightly mystified given that fetching the WSDL is usually a one-off 
cacheable activity - the endpoint of service itself would still be 
slashdotted and i'm not sure that's a problem to be solved in this WG 
either.

Paul

-- 
Paul Sumner Downey
Web Services Integration
BT Exact




-----Original Message-----
From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org]On
Behalf Of Yaron Y. Goland
Sent: 18 March 2004 03:54
To: Martin Gudgin
Cc: Downey,PS,Paul,XSJ67A C; ryman@ca.ibm.com; www-ws-desc@w3.org
Subject: Re: WSDL Import/Include Locations



There are two goals in this area I think WSDL needs to achieve:

Goal #1 - Location Redundancy
Goal #2 - Load Balancing

It is clear now to me from the comments on the list that Goal #1 can be 
achieved today by WSDL as is. But I am still concerned that Goal #2 
cannot be reasonably achieved.

Received on Friday, 19 March 2004 08:51:46 UTC