RE: Scoping multi-transport / async bindings for WSDL

> Actually, there is another important question I tried to 
> illustrate with
> the expenseReport example - Should we support patterns where 
> operations
> of a single interface may be bound to different binding types (for
> example, one for soap/http, one for plain http, etc)?

Yes, agreed - essentially they are similar questions at two different
scopes.

I can't help but once again feel somewhat depressed/disheartened that we
didn't restrict WSDL to describing only SOAP, and expand the space of
the possible SOAP bindings to include mappings to "straight" HTTP.  That
would have reduced these two problems to one....

Anyway, let's discuss on the call.

--Glen

Received on Wednesday, 9 February 2005 15:17:26 UTC