Entries:
Comments:
Posts:

Loading User Information from Channel 9

Something went wrong getting user information from Channel 9

Activity Profile

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

Posted: Apr 15, 2010 at 2:48 AM
By: Matthijs Hoekstra
Avg Rating: 0
15,908 Views
2 Comments
reddit

Tweet

1 hour, 18 minutes, 8 seconds

format
< > embed
+ queue

Sign In first to access your queue.
Close

Sorry, video was not added to the queue, an error occurred. Please Contact Us and let us know.
Close

Embed code for this video

Copy the code above to embed our video on your website/blog.

Video format

Option selected may change based on video formats available and browser capability.

Auto
Use our suggested format for this video.
Smooth Streaming
Adaptive bitrate streaming - little buffering but lower video quality at times of low bandwidth. Silverlight 5 required
Progressive
Traditional buffered video format. Silverlight 5 required
HTML5
For browsers that support H.264 MP4 or WebM video playback such as:
IE9+, Firefox 4+, Chrome 5+, or Safari 4+.
Flash
For browsers that have the Adobe Flash Player plugin installed.

Download

Right click “Save as…”

WMV (WMV Video)

File size
1.4 GB
MP3 (Audio only)

File size
35.8 MB
MP4 (iPod, Zune HD)

File size
283.1 MB
Mid Quality WMV (Lo-band, Mobile)

File size
389.6 MB

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.

62fb4e66-1b96-43e8-b5ce-8642c96afdf8[1]

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

Follow the Discussion

Follow
Oops, something didn't work.

Try again?

Sign In to be begin to follow these comments

What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in. You need to be signed in to Channel 9 to use this feature.

Getting "follow" information

Stop following these comments

Start following these comments

What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in and view them all on your notifications page.

Removing your "follow"

Setting up your "follow"

Did you know you can
sign up for email notifications?
- Subscribe to this comments

albertindian

May 27, 2010 at 11:05 AM

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
Kannan

Dec 25, 2010 at 4:29 AM

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.