Intro to REST

[fanbondiK]

Your definition of Idempotent is not complete, in addition to multiple times you should add "the outcome of the results is not changed" e.g. max(x,x) = x.

[fanbondiK]

Seems he is reading, BTW it a great video..

[dvuo6720]

hey this vid is awesome. I learnt a lot of this stuff during my first semester of my first year at uni :)

[happpymedy]

Only now, I can REST peacefully

[duminicad]

@happpymedy #LOL good one!!

[nitinpai2000]

Thanks for the tutorial Joe. However I feel you could have given more emphasis on state. My understanding is that, State refers to application state, and application state is represented by document (Representation). Each state leads to next state through an action (Method) in the form of links in the document.

Thanks,

Nitin

[nitinpai2000]

Also a thought. Intermediaries like proxy act like a server when caching is in place. They hold the part or entire application state, and transfer these states when user agent requests state transition (via GET, DELETE or PUT).

Please correct me if I have got something wrong in this concept....

Thanks,

Nitin

[ThirdRomeAquilo]

wtf is this bullshit? REST?? oh come on. Next some jackass will try to rename 'network' into 'cloud'.

[lakc24]

The tutorial is good, but difficulty to understand his speech with his soft voice and difficult to distinguish the exact words. YT transcribe audio is also not so helpful as well. need a better presenter. Perhaps increased sound amplification would be better.

[vishalindia1970]

This is really a gr8 video, very informative from Architect's point of view as well.

Though I have a question: In the end you talks about uploading a large image with a new URI and deleting the previous one. The question is, the resources refering to the previous image will break, how do u address that?

Rgds,

Vishal

[TraceTreez]

Why are you wearing makeup?

[sassoleo]

@TraceTreez It is a design constraint

[wizardpoop]

@TraceTreez Wonder where he was the night before...



[ZULF1000]

Good teacher, i wish you spoke a little slow thought. I felt like i was learning how to listen faster....

I will need to watch this video a few times before i can start getting the technical concepts you are talking about.

[ScrewAttackChina]

nice eye liner

[mariegriffiths]

I liked the intro and your mascarra.

[gonzalemario]

why he needed to speak so low?

[carnagerpm]

there is a volume control on your computer learn to use it.

[reinpost]

@carnagerpm doesn't go up beyond a level where my processor fan isn't drowning out the presenter's voice

[CusterFlux]

Hello Google, please start respecting your audience's ears!

I can't bloody well hear what he's saying, if you're going to go through all the trouble of producing a video, at least take a few seconds to clip on a proper mic: if it's a struggle to hear, you've just wasted everybody's time and frustrated your audience - or made them deaf when their email alert blasts their ears out because they had to turn up so damn much to compensate.

[carnagerpm]

STFU

[Angelvinni]

smart.

[635574]

at 2:43 the subtitles come out of sync

[jaeshaib]

iirc it was not. It became out of sync recently

[neomagicfish]

ya!I agree

[ganezt]

WHAT HAPPEN TO THIS VIDEO..... SOMEONE PLZ MAKE IT PLAY !!!

Please

[ganezt]

thank you guys !

[hli29]

Thanks, good clear presentation

[mariote69]

Please Subtittle in Spanish... my english ear is so slow... Thanks for the introduction...

[C7B27D7B4]

i love the emphasis on self-identifying responses (content-type header, contains uris, ...); i also love the coverage of method characteristics (safe, idempotent, cacheable, ...); this clarifies the relationship (and advantages) of REST with the overall architecture of the internet; thanks for being so clear and to the point :-)

[jcgregorio]

dalvac,

1. Use POST for creating or updating resources, things you wouldn't want cached.

2. GET requests don't have a body so all the info has to go into the URI via the query parameters.

[irab]

Really enjoyed this Joe. Thanks for sharing.

[dalvac]

Last question for now:

4) Why does Ajax use XML-RPC instead of a restful protocol like AtomPub, which takes better advantage of the Rest architecture?

[mxrss]

XML-RPC is not that robust for AJAX you should consider using JSON serialization for the your objects that you want to return. Remember all processing with AJAX is done through Javascript on the client, and XML reader is not the best on the client, json serialization is better.

[dalvac]

One more question:

3) Is not clear on the slides: Is XML-RPC restful?

[jcgregorio]

No, it is not.

[dalvac]

123 testing

[dalvac]

Hi Joe, this was perfect!

Thank you!

This is for anyone who can help:

1) I would like to know when is better to use post rather than get, since post is not safe, nor cacheable and nor idempotent and get is.

2) When a html form uses the get method to submit, the whole url appears in the bar address of the browser, while using the post method this doesn't happens.

Why does this happen this way?

Thank you in advance!

[lloydbrookes10]

brilliant, thanks joe.

[nogwater]

This is my comment on this video.

[BuddhaHippie]

That was.... technical...