Loading...

RESTful API Design - Pragmatic REST - Webinar

17,131 views

Loading...

Loading...

Transcript

The interactive transcript could not be loaded.

Loading...

Loading...

Rating is available when the video has been rented.
This feature is not available right now. Please try again later.
Published on Sep 30, 2011

If you are having audio issues on youtube, you can watch it here: https://vimeo.com/23861183
Download The API Design eBook: http://bit.ly/WijbEd

Comments • 13

Jorge Wander Santana Ureña
What time the sound back is? :/
Kalle Johansson
Ok, seems to be the same uploaded once again, could not hear any sound after the first few seconds. Give it another go will you, please.
Biruté Awasthi
Looks like file on youtube got corrupted and audio disappeared... We'll work on having this fixed in the next couple days. Sorry about that.
Kalle Johansson
I think there might be an issue with the sound, try uploading again ?!
Marsh Gardiner
John, right on—that's a great point. We cover this in later editions, but we should have called that out here. For anyone reading the comments, pay attention to what John explains above.
shideon1
Btw, I agree with the notion of focusing on your API's design regardless of if it follows REST, however, following the htt.p spec is important.
shideon1
You oversimplified PUT vs. POST. They aren't directly mapped to CRUD at all. It depends on whether you know the resource's location. You PUT an entity to be stored as a resource somewhere i.e., you know the URI ahead of time, You can use PUT for creating or updating. You POST an entity and it's resource can be decided by the server if not passed (and preferably returned in the "Location" header if a new resource created). Can be used for creating or updating,
Jerrod Horton
Great Webinar. The only thing I might argue is the way you prefer your searching. Searching for resources is something I have found to be a common business case. I am about to roll out a service query pattern that goes something like this: /resourceAs?Query={query} where the query is VB like syntax that allows the consumer to write a "SQL'esk" query against the resource collection. For example: /employees?Query={Name = Bob AND Salary <= 100000 AND Manager.Name = AL} Great stuff guys. APIs FTW
Ali Moeeny
I loved the "don't code like my brother" thing
Vinod Jayendra
nice. Can you post similar videos on other subjects as well 
When autoplay is enabled, a suggested video will automatically play next.

Up next


to add this to Watch Later

Add to

Loading playlists...