• To: 'Michael Champion' <michaelc.champion@g...>, 'Dare Obasanjo' <dareo@m...>, xml-dev@l...
• Subject: RE: What Does SOAP/WS Do that A REST System Can't?
• From: "Bullard, Claude L (Len)" <len.bullard@i...>
• Date: Wed, 30 Mar 2005 11:33:12 -0600

Thanks Dare and Michael.  So WS is pre-rolled 
and REST is roll-your-own.  The contents of the 
package are dealer's choice.

I want to know what others have to say.  I think 
you are saying that there is a complexity trade-off; 
that is, if you don't need a, b and c, REST 
is easier and faster to develop.  OTOH if 
you buy WS* does a, b and c and you get to 
spend more time on the content as long as you 
are happy with vendorZed's implementation of 
a, b and c.

<toNoOneSpecifically>
Can we keep this on a technical plane please?  I'm 
not trying to start a fight; I need to be wiser about 
this topic in terms of trade-offs.  Various flavors 
or vendors of WS* aren't the topic of interest to me 
unless they critically affect a technical tradeoff.
</toNoOneSpecifically>

len

• Follow-Ups:
  • Re: What Does SOAP/WS Do that A REST System Can't?
    • From: Michael Champion <michaelc.champion@g...>
  • Re: What Does SOAP/WS Do that A REST System Can't?
    • From: Leigh Dodds <leigh@l...>
  • Re: What Does SOAP/WS Do that A REST System Can't?
    • From: David Carver <d_a_carver@y...>

• Prev by Date: Re: What Does SOAP/WS Do that A REST System Can't?
• Next by Date: Re: XQuery Adoption Survey Results
• Previous by thread: RE: What Does SOAP/WS Do that A REST System Can't?
• Next by thread: Re: What Does SOAP/WS Do that A REST System Can't?
• Index(es):
  • Date
  • Thread