web services - why WS-I profile specification is specific to SOAP encoding -
web services - why WS-I profile specification is specific to SOAP encoding -
there 1 thing confused reading ws-i profile specification. ws-i institute aimed interoperability between web services..as per understanding web service can defined in wsdl per rules of ws-i profile specification....now wsdl\ws-i supposed independent of info , transport binding. , soap 1 way of info binding not way of info binding.
why ws-i profile explicitly cover soap info binding protocol? why ws-xxx specifications talk in terms of soap protocol headers? why did n't ws-i profile describe various headers in info binding independent way? in word, there difference between soap , web services?
q: there difference between soap , web services?
a: there's huge difference (unless you're marketing dept in microsoft ;))
the main alternative soap rest (i.e. rest-ful web services)
here 2 first-class overviews of ws-interoperability, 2 different perspectives:
http://msdn.microsoft.com/en-us/library/ms953977.aspx
http://www.infoq.com/news/2010/11/wsi-closes
web-services soap
Comments
Post a Comment