[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: What Does SOAP/WS Do that A REST System Can't?
Mu. REST is a protocol, SOAP is a message format. <duck> Less pedantically, as people tend to use them in practice, WS-* builds a lot of capabilities (pretty much one capability for each WS spec) into the infrastructure. REST leaves them up to the application builder, except for those you get "for free" with the Web infrastructure such as HTTP authentication, HTTPS, etc. (If those don't work for you, e.g. you need end to end encryption rather than the point to point encryption that HTTPS provides, you are on your own). Basically REST offers a discipline for making lemonade out of these lemons, whereas WS-* offers a wide range of genetically modified sweet lemons that you can supposedly eat right off the tree. On Wed, 30 Mar 2005 10:36:22 -0600, Bullard, Claude L (Len) <len.bullard@i...> wrote: > After all the threads on this, I can't remember ever > seeing this question answered. Can someone point me > to a list of the capabilities that one gets using > SOAP/WS* that one won't get using REST? > > len > > ----------------------------------------------------------------- > The xml-dev list is sponsored by XML.org <http://www.xml.org>, an > initiative of OASIS <http://www.oasis-open.org> > > The list archives are at http://lists.xml.org/archives/xml-dev/ > > To subscribe or unsubscribe from this list use the subscription > manager: <http://www.oasis-open.org/mlmanage/index.php> > >
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|