The long-term "storecast"

Jeff has posted some SOAP samples

Most of the sample code that Jeff, Jason and David Robinson have posted so far show you how to use the REST interface when coding against SSDS.  Jeff has just posted his first SOAP example here.  We are interested in finding out how many out there will build against REST and how many will build using SOAP.  What are the considerations when you think about using one or the other?  How can we make these interfaces better over time?  These are some of the questions we have in our mind.  Would love to hear from you.
Published Thursday, April 03, 2008 3:50 PM by kellyalt

Comments

 

rogerj said:

I prefer the REST approach for simplicity and low overhead with data retrieveal having minimal or no security requirements (e.g., public catalog data or the like).

I'd use SOAP with the WSHttpBinding only when the WS-* features were important.

I would guess my applications would be 1:10 SOAP:REST.

--rj

April 3, 2008 2:50 PM
 

rogerj said:

SOAP is showng somewhat better performance than REST, especially with large payloads. There also are unexplained LINQ to XML performance issues with base64Binary encoding of even small bitmaps.

I should have added to my previous message "when SSDS implements WS-* features such as digital signatures and reliable messaging."

--rj

May 2, 2008 1:02 PM
Anonymous comments are disabled

This Blog

Syndication

© 2008 Microsoft Corporation. All rights reserved. Terms of Use  |  Trademarks  |  Privacy Statement
Microsoft
Page view tracker