[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: SOAP and the Web

• To: "'xml-dev'" <xml-dev@l...>
• Subject: RE: SOAP and the Web
• From: "Andrew Dubinsky" <andy@e...>
• Date: Thu, 2 May 2002 13:37:31 -0500
• Importance: Normal
• In-reply-to: <3CD17C71.6358F953@p...>

> Andrew Dubinsky wrote:


> > 
> > Does this criteria imply that all REST component methods 
> must define 
> > standardized API's prior to deployment?
> 
> There is no need to define them. Except for the rare case 
> where you have an extremely unique need, you use the methods 
> built into the REST-aware protocol you are using. Today that is HTTP.

<snip>...</snip>

I was not talking about the interface in the sense of protocol. That is
intrinsic to the protocol handler, hopefully far below the application
developer's view. In talking about interfaces, I meant to examine the
issue in a COM interface sense. Much of the problems I see with both
SOAP and REST are the lack of a guaranteed, versioned interface contract
between developer and service consumer. Methods and their parameters
change over time. Can REST create a strongly interfaced version system
if the entire access method resides in the URI? Is that part of the
specification? Should it be?

Sincerely,
Andrew Dubinsky

• Follow-Ups:
  • Re: SOAP and the Web
    • From: Paul Prescod <paul@p...>
  • Re: SOAP and the Web
    • From: "Didier PH Martin" <martind@n...>

• References:
  • Re: SOAP and the Web
    • From: Paul Prescod <paul@p...>

• Prev by Date: Re: SOAP and the Web
• Next by Date: Re: Re: I can XInclude where I bloody want to
• Previous by thread: Re: SOAP and the Web
• Next by thread: Re: SOAP and the Web
• Index(es):
  • Date
  • Thread