• To: "Bullard, Claude L (Len)" <len.bullard@i...>
• Subject: Re: What Does SOAP/WS Do that A REST System Can't?
• From: David Carver <d_a_carver@y...>
• Date: Wed, 30 Mar 2005 12:40:20 -0500
• Cc: xml-dev@l...
• In-reply-to: <15725CF6AFE2F34DB8A5B4770B7334EE07206D59@h...>
• References: <15725CF6AFE2F34DB8A5B4770B7334EE07206D59@h...>
• Reply-to: d_a_carver@y...
• User-agent: Mozilla Thunderbird 1.0 (Windows/20041206)

><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>
>  
>
There are several articles discussing this very topic on XML.com.  In 
some ways, a REST architectural style, is simpler and easier to 
implement than a SOAP interface.  The last web services type application 
I developed, was solely based on REST as it didn't need the extra stuff 
that SOAP involved, the standard protocols were secure enough.  I might 
also suggest taking a look at EBXML and their messaging standards as an 
alternative to just SOAP.

Dave

• References:
  • RE: What Does SOAP/WS Do that A REST System Can't?
    • From: "Bullard, Claude L (Len)" <len.bullard@i...>

• Prev by Date: Re: XQuery Adoption Survey Results
• Next by Date: Re: What Does SOAP/WS Do that A REST System Can't?
• 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