http://mschnlnine.vo.llnwd.net/d1/Dev/App_Themes/C9/images/feedimage.pnghttp://channel9.msdn.com/posts/rojacobs/endpointtv-SOAP-and-REST-a-Perspective/endpoint.tv - SOAP and REST a Perspectivehttp://channel9.msdn.com/posts/rojacobs/endpointtv-SOAP-and-REST-a-Perspective/en-usWed, 06 Aug 2008 07:06:20 GMTWed, 06 Aug 2008 07:06:20 GMTEvNet (EvNet, Version=1.0.3608.3122, Culture=neutral, PublicKeyToken=null)Excellent&nbsp;interview Ron,<BR><BR>I liked the notepad example.&nbsp; Looking forward for your endpoint podcasts.<BR><BR>http://channel9.msdn.com/posts/rojacobs/endpointtv-SOAP-and-REST-a-Perspective/?CommentID=419841Wed, 06 Aug 2008 07:06:20 GMThttp://channel9.msdn.com/posts/rojacobs/endpointtv-SOAP-and-REST-a-Perspective/?CommentID=4198410http://channel9.msdn.com/419841/WebViewBug.aspx?EVT=0Excellent&nbsp;interview Ron,I liked the notepad example.&nbsp; Looking forward for your endpoint podcasts.Jomit Vaghela0http://channel9.msdn.com/419841/Trackback.aspxFor practial purposes, SOAP is a superset of REST.&nbsp; The key limitation of REST is the operations which are limited to what HTTP supports.&nbsp; Like anything else even those limits can be hacked away and actually are by FORM style web processing.&nbsp; But REST sticks with a small number of basic operations on addressable resources, get, put (insert), post (update), and delete.&nbsp; These operations are the same ones used to access relational databases.&nbsp; The alterative that used to be in much more favor is a distributed object model along the lines of DCOM where you have network communication that involves remote references to objects and complicated state models between objects that cooperate across the net.&nbsp; For all the noise, Microsoft's strategy seems strongly in tune with the REST model.&nbsp; You see that in the way that LINQ, ADO.Net Data Services, and the Entity Framework operate.&nbsp; Data is separated from behavior,&nbsp;modeled as sets of entities, and made network addressable.&nbsp; The operations on data are those used by REST and also by traditional databases.&nbsp; So the decision between REST and SOAP will mainly revolve around the particular environment that you are working with and the supporting function that is easiest for you to use.http://channel9.msdn.com/posts/rojacobs/endpointtv-SOAP-and-REST-a-Perspective/?CommentID=419745Tue, 05 Aug 2008 14:56:02 GMThttp://channel9.msdn.com/posts/rojacobs/endpointtv-SOAP-and-REST-a-Perspective/?CommentID=4197450http://channel9.msdn.com/419745/WebViewBug.aspx?EVT=0For practial purposes, SOAP is a superset of REST.&nbsp; The key limitation of REST is the operations which are limited to what HTTP supports.&nbsp; Like anything else even those limits can be hacked away and actually are by FORM style web processing.&nbsp; But REST sticks with a small number of&#8230;dnjake0http://channel9.msdn.com/419745/Trackback.aspxNice Interview.<br><br>So to sum up some of the considerations in choosing both :<br><ul><li>Security</li><li>URI Length (Remember URL can be at max 2K)</li><li>Type of Consumer Clients (Lot of Javascript/Air/Silverlight calls)<br></li><li>Complexity of Return Types</li></ul>Anything more ??<br>http://channel9.msdn.com/posts/rojacobs/endpointtv-SOAP-and-REST-a-Perspective/?CommentID=419647Tue, 05 Aug 2008 04:42:21 GMThttp://channel9.msdn.com/posts/rojacobs/endpointtv-SOAP-and-REST-a-Perspective/?CommentID=4196470http://channel9.msdn.com/419647/WebViewBug.aspx?EVT=0Nice Interview.So to sum up some of the considerations in choosing both :SecurityURI Length (Remember URL can be at max 2K)Type of Consumer Clients (Lot of Javascript/Air/Silverlight calls)Complexity of Return TypesAnything more ??Parag Mehta0http://channel9.msdn.com/419647/Trackback.aspx