Loading user information from Channel 9

Something went wrong getting user information from Channel 9

Latest Achievement:

Loading user information from MSDN

Something went wrong getting user information from MSDN

Visual Studio Achievements

Latest Achievement:

Loading Visual Studio Achievements

Something went wrong getting the Visual Studio Achievements

Why REST? by Aaron Skonnard

1 hour, 18 minutes, 8 seconds


Right click “Save as…”

As REST continues to grow in popularity, it’s important to stop and ask yourself why REST? REST is by no means a silver bullet but it does offer some advantages over traditional SOAP and WS-* architectures when it fits well into your scenario. There are also times when SOAP makes more sense because it offers features and capabilities that REST cannot provide. In the end, REST and SOAP are different architectural styles, each with their own pros and cons. Come and learn when to choose one over the other and why REST makes sense for many Web services.



This session is presented by Aaron Skonnard during Microsoft DevDays 2010 in The Hague in The Netherlands.



Follow the discussion

  • Oops, something didn't work.

    Getting subscription
    Subscribe to this conversation
  • Aaron,

    Want to ask some questions about REST.


    REST specifies that the URI must be understandable and must use resources as endpoints.


    Below is the scenario. Suppose i need to search data by company name and company name contains characters like & or /. These are restricted characters in terms of URl. / specifies subpath and & specifies the queriy parameter collection


    How can we implement this in REST

  • KannanKannan

    Can someone re-upload this video. There is some media failure error

Remove this comment

Remove this thread


Comments closed

Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums, or Contact Us and let us know.