Great talk! This completely laid out everything about REST APIs. With reasonable best practices too. Best practices that are indeed true to Facebook, Twitter, Google REST APIs. Thanks a lot for this.
I'd additionally: 1. Use X - header field instead of parameters like _body (for example X-H TTP-Method) 3. In post response return only Location to resource, no content. Well configured API client will follow redirection and fetch new resource (including browsers) 4. Use absolute or even relative links in JSON (no need to include domain) 5. Use PATCH for partial updates, and POST for issuing actions on resources. 6. Use underscore instead of camel case in JSON (readable; ruby client?)
Very nice and informative talk. One question on security aspect; what are the best practices (or what are the practices Stormpath follows) to handle XSS and CSRF? Thank you.
+Daniel Lima de Almeida there are several reasons as mentioned in the video. A few of those are - Metered API's - Not required in all (most) instances - Reduce serve latency
Great talk! This completely laid out everything about REST APIs. With reasonable best practices too. Best practices that are indeed true to Facebook, Twitter, Google REST APIs. Thanks a lot for this.
Missed a quote before the value at 31:55
Awesome video. Just want I needed while getting started on designing a REST+JSON based service.
In nodejs I hope
I'd additionally:
1. Use X - header field instead of parameters like _body (for example X-H TTP-Method)
3. In post response return only Location to resource, no content. Well configured API client will follow redirection and fetch new resource (including browsers)
4. Use absolute or even relative links in JSON (no need to include domain)
5. Use PATCH for partial updates, and POST for issuing actions on resources.
6. Use underscore instead of camel case in JSON (readable; ruby client?)
Very nice and informative talk. One question on security aspect; what are the best practices (or what are the practices Stormpath follows) to handle XSS and CSRF? Thank you.
rfc 5789 is not without undefined use-cases, I think there will be another rfc supplementing (or replacing) it
I know rails 4.0 has embraced Patch as their defacto update method, which might help push the rfc 5789 forward..
Excellent talk, and great information. Thanks!
Great video! are the slides posted anywhere?
Amazing talk! Thanks
Why does everything have to have hrefs spit out?
Why is it that I can't just ask for an account (for example) and have everything expanded by default?
+Daniel Lima de Almeida there are several reasons as mentioned in the video. A few of those are
- Metered API's
- Not required in all (most) instances
- Reduce serve latency
Hmm...partial updates are totally idempotent in my book.
Thanks this was pretty helpful
The convention is to use underscores instead of camelCase in JSON.
that is not true. Even though there is no offical standard, it's observed that camelCase is the way to go
found it thanks!
If you are a newbie trying to learn about H TTP and REST, then take all of this with lots of grains of salt.