Re: Back to Requirements (was RE: Web Service Definition [Was

Mark,

I cut-n-pasted from the version started by Krishna, Heather
and others. I would have no problems removing the 's' at this
point as I'd prefer that we table the discussion and focus on
the goals and requirements. All I was trying to do here is
put forth a proposal that "we can live with" for the time
being.

Cheers,

Chris

Mark Baker wrote:

>>Why is it critical that a web service have only one interface?  I don't know
>>of any mechanism by which there could be more than one, but what would be
>>the problem with that if someone figured out how to do it?
>>
> 
> Because the "Web way" to do this is to have a different URI for each
> interface.  That is, if we had some chunk of software that had both an
> operational interface and an administrative interface, we'd give a URI
> to each.  Of course, this design pattern (can't recall the name) has
> also been used by other component systems in the past, such as COM (I
> believe).
> 
> I'm just wondering if this was a case of "why not support multiple
> interfaces?!", "we definitely need it because ...", or "oops, hit the
> 's' key". 8-)
> 
> MB
>

Received on Wednesday, 6 March 2002 07:40:51 UTC