Intro to REST

[@sebastiansimon7557]

3:16 “Idempotent means the request can be done multiple times”. Well, anything can be done multiple times. The key characteristic of an idempotent request is that repeating a request doesn’t affect the outcome of the request itself (if at least the final request is completed successfully). In other words, a request is idempotent if it doesn’t matter whether you do it once or multiple times and the result will be the same. E. g. GET is idempotent, POST isn’t.

[@vincentmo652]

Very clear and detailed explanation, not over-simplified like many others I watched. Much appreciated, thank you.

[@naveenautomationlabs]

Learn Application Programming Interface Concept: kzbin.info/www/bejne/gobFc56ffs2le5Y What is an API? Why we use API? How we use API? When we use API?

[@ImmaShadowGirl]

This was uploaded 7 years ago. It's pretty great when we look at it that way.

[@abssey1]

Exactly!

[@MFM88832]

@@abssey1 Your comments are 7-8 years ago. They are pretty spot on when we look at it that way!

[@Bliced]

looking for a vid to put me to sleep. this did the trick.

[@inkeotv]

Bliced and it does not answer what RESTful means!

[@stacydegeus6248]

s

[@stacydegeus6248]

s

[@xZr993]

+Bliced Thank you for making me look at the comments and giggle, +Aras Geylani Thank you for saving my time

[@Eichro]

if you're sleepy, you should... ...REST

[@widebandrecords902]

As a 15 year plus programmer, i would say most of information about REST/api services etc are great if you have something to work with like a business... Google are so smart in making many programmers change their thoughts of being a creator to now simply wasting time on creating apps etc that are soo dependent on google, cdn's etc... I was born in the 80's so i will always be a creator rather than a follower, and the reality is that the tech world has become server driven more than ever, what happens if/when isp's get really expensive?

[@anis.lounis]

Wideband Records Well said ^^

[@sandarabian]

I guess that's just the nature of the business, as more wheels are made, there will be less reasons to re-invent them.

[@jasonsharp4950]

more use cases for wheels requires ever more innovative wheel design, not the same old wheels.

[@joaquincespedes7151]

Finally i found a good explanation about this subject

[@jasonlough6640]

From a programmers (as compared to an engineers) perspective, is it safe to say that REST just means you use GET / POST variables? And a RESTful API means a library that uses GET / POST vars? So many job postings say they want someone with experience with RESTful APIs and you get there and even they cant tell you what that means. Just say you need someone to write stuff that interacts with a database and forms on the web.

[@CompumatrixUsInc]

Exactly. They had to go as far as calling it REST or RESTful when it was simply utilizing GET/POST.

[@jonathangoodman9751]

This video covers REST however it doesn't exactly cover API's.

[@mikeshinoda2806]

+Jason Lough the term was strange to me too ! I did many searches for it

[@jasonlough6640]

Id like to add that REST also involves application to application communication. App A exposes some functions (like www.example.com?function=foo&x=4), App B exposes some functions. Both reply with a JSON object. You can get A and B to talk to each other. REST in a nutshell.

[@BillMavromatis]

@Jason, it's all buzzwords...

[@obsidiansiriusblackheart]

This was a wonderful video, one of the best I've seen on rest

[@MsOwenMeany]

This is a good intro. For "The Afghan" and others, read Fieldings thesis. As it stands now the hypertext transfer protocol is the prime example of a REST design.

[@mrankushbhalotia]

Great video! Tells you all you need to know in a very short duration.

[@JoeGregorio]

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.

[@alfieroseburg8887]

Very informative video on rest and I am sure you are the master on the subject.

[@breebw]

7:15 Just to bring this upto date, add various NSA proxies between the user agent and origin server.

[@kelekokerupuk]

Your Video Is Very Useful Sharing Joe Gregorio goes over the basic principles behind REST.

[@macfelix9202]

This is perfect. Exactly what I was looking for. Thank you!

[@arttuladhar007]

Great Video !! Lots of core concepts explained in simple way.

[@RedShipsofSpainAgain]

Great vid. But the subtitles cease synching around 2:44 with the audio, which makes following them subsequently annoying.

[@prettyprinted]

Good video with useful information. I didn't think it was as boring as others though in the comments.

[@dojohansen123]

@Jason Lough: I think you may want to watch the video again. :) Programmers who are concerned only with *consuming* an API mainly need to understand the API itself. The content in this video is aimed at people who are desiging the APIs. Basically the message is "when designing a web API, make sure you know HTTP so you can work with the architecture and reap the benefits". He provides an example showing us why XMLRPC is *not* RESTful and thus not in the architectural style of HTTP, and how this means you lose benefits such as caching in the infrastructure. Recruiters thus need to know if they are looking for someone to consume APIs or someone to design them. The former is considerably less demanding than the latter! Designing good APIs is difficult, and usually far more important to get right than code consuming APIs, since the consuming code can be changed with ease whereas redesigning APIs has repercussions for everyone who are using it.

[@promatic-code]

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

[@venkatbrundavanam2013]

Great video with lot of basic concepts covered

[@jassu54]

Thank you Joe , Its a good explanation . Got good idea on REST

[@diegoalvarezcorreia958]

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?

[@promatic-code]

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

[@8a1ad61b]

This is "Intro to HTTP"

[@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

[@janeharrison3010]

him looking so tired is making me tired

[@dojohansen123]

@Nikhil Manhas URI = Uniform Resource Identifier. A URL is a kind of URI, so every URL is a URI (in exactly the same sense that every cat is a mammal). When a thought pops up, maybe try to assess it before jumping to conclusions! Which is more likely, that Google Code is just a bunch of clueless marketing people, or that the thing you'd never heard of is indicative of your own ignorance? I really don't mean to sound as harsh as that does! It's just friendly advice, and advice that I try but often fail to follow for myself! Luckily we live in a time when a quick fact check is often possible, at least for such well-defined questions as "what's a URI? isn't it URL?" - Google "uri wiki" and feel lucky. Reading just the first sentence or two of the summary will suffice to clear up the misunderstanding!

[@RyanABoyles]

Really enjoyed this Joe. Thanks for sharing.

[@reinpost]

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

[@daruberden]

Thanks, Sandeep ^) It was a rhetorical question because what i hear in this video is not an Intro to REST. I really wanted to know what it actually is but got nothing out of this video as a beginner. So IMHO this is not actually an INTRO.

[@Zp00kie]

Mascara. Now made fashionable for developers.

[@bikashkarmakar7117]

This is conceptual tutorial for senior developers..

[@couchTube4]

I want to party with this guy. He looks like a hoot!

[@olegruno9608]

"In the same way, the REST architectural style is a set of architectural constraints you would see in a protocol built in that style. HTTP is one such protocol." HTTP is build on constrains of the rest? I do not understand. Rest is build as number of constrains over http. Am i right?

[@rohitjagannath5331]

Good Video. Helped me connect the dots on REST. Not completely though but this helped.

[@diegoalvarezcorreia958]

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!

[@jaumecoxi9275]

I like the tone of the guy's voice.

[@sassoleo]

@TraceTreez It is a design constraint

[@muthuGowriShankar]

Thank you so much. It was crystal clear

[@diegoalvarezcorreia958]

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

[@bitcode_]

you can tell Google has already sucked the living soul out of him

[@ricmccorriston9302]

Is Joe wearing makeup?

[@mickymc7354]

I was thinking the exact same time, def has some emo eye liner on

[@eugenenovikov671]

i also thought his eyes in make up, and so .... emmm.. voice.

[@eugenenovikov671]

***** metalheads are brutal, he is glam rocker may be

[@eugenenovikov671]

***** it is true makeup - it appears by itself when need

[@eugenenovikov671]

***** my friend in night clubs use eyeliner in wc to make gothic make up, it is usual thing. Cap Sparrow uses it too

[@madhes23]

Fun fact: When this video was uploaded, there was no Instagram, Snapchat, WhatsApp etc.

[@08Pixel]

Characteristics of RESTful protocol 4:34

[@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.

[@xx1010guyxx]

Only now, I can REST peacefully

[@IsidroMoran]

What's with the eyebrow threading?

[@firatkucuk]

There's synchronization problem in translation script.

[@wizardpoop]

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

[@jreylbc1]

Thank you. That was informative and interesting.

[@SkGow]

Cool. Very Well presented

[@08Pixel]

Starts at 0:12

[@hli29]

Thanks, good clear presentation

[@fozzarelo]

Can't learn anything from this guy.. can't get past the eye liner and the blush!

[@KurtDasBastard]

Just a light base. I think it pops!

[@RefinedCode]

Awesome video!

[@PerryCS2]

Volume is SO low... when this video is done I hope I remember to turn it down so I don't blow my speakers... LOL...

[@cinilaknedalm]

This sounds like something someone written to explain something to themselves, but not too anyone else. It assumes too much knowledge and gives too much detail, which sounds just like jargon to someone trying to understand this. Don't think the creator understands the term 'Intro'

[@toddsherman]

'Intro to REST' from 'Google Developers'. So in this case, the introduction bar is higher because they are addressing developers.

[@adityapipersenia]

Todd Sherman Just because a video is posted by 'Google Developers' doesn't imply that its meant to be understood by only developers.

[@ThomasCuvillier]

My take is that the first half is for non developers, the other is for newbie developers. It sums up everything nicely for students but I agree it feels weird somehow.

[@toddsherman]

pipermania It's clear that developers are their target. They post things relevant to Google's developer products (Check their About page). Also, on the Google Developer's site it says "Inspiring developers everywhere."

[@tarinshah2960]

very fast for first timers

[@nikitausefi2061]

That was a great tutorial

[@xgqfrms]

Introduction to Google Sign-In for Websites

[@ramshambo2001]

Thank you very much for this video!

[@SandipDas30]

how does that matter? or relevant here?

[@ganesht]

thank you guys !

[@fanyang2159]

oops, the subtitle didn't follow the voice.

[@AchilleasTheOfficial]

Wow that was great, thanks :D

[@ghezalahmad]

AGAIN, I have the same question, what is REST? I could not get you, sorry!

[@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.

[@mredbishop]

The outcome of the results may change but the response does not. Case in point, delete is idempotent.

[@neomagicfish]

ya!I agree

[@ganpati0007]

Wanted To Understand REST but this guy talks abt many other topics in the first 5 minutes that I don't know

[@DiegoDora]

Great video!! Thanks

[@daruberden]

so WHAT IS REST?!

[@vanderszpak]

2008, wow!

[@an1792]

thank you so much

[@ganesht]

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

[@marionpierce3427]

I can't hear shit.

[@badymojoy]

Seriously--the volume needs to be normalized.

[@LalitMali]

exactly

[@dominik1023]

Not to sound negative, but as a fellow instructor I will tell you that you need to show passion and present a boring subject in an engaging way.

[@ariemariedalleis464]

I'm inclined to agree. The content seems good, but I'm not convinced he cares.

[@eugenenovikov671]

dont use make up, we dont want tto know your secret life.

[@ia9115]

FIX the sound!

[@Alwsmith]

He is totally wearing makeup I was thinking the same thing!

[@matthewlind4908]

boring, but informative

[@malikperang6820]

very nice!

[@ifudiscusswithmeurprobably7273]

The first thing i thought was ... stargate atlantis mckay

[@mariote69]

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

[@lordlonghurst]

lovely

[@ajnikhil]

Why he says URi ?? it's URL = Uniform resource locator. Guess marketing people at Google are doing technical jobs.

[@jameswoodruff6920]

a URL is a type of URI. Pre-Google.

[@tabshiftescape]

vimesx buuuuuuuuuuuurrrrrrrrrrrnnnnn

[@xxxxxGhostBoyxxxxx]

Congratulation Nikhil Manhas, u just showed the world your stupidity and ignorant. URI stands for Identifier not, Locator. For an idiot, let me keep this as simple as it could be. URI will be identified when a protocol does not associates in it, e.g support.example.com. That's URI but it will be an URL if you put support.example.com or support.example.com/idiot.html that is also considered as URL. Now, go to school.

[@ajnikhil]

thanks for the knowledge, but kindly f***off

[@xxxxxGhostBoyxxxxx]

Nikhil Manhas ignorant yet pathetic.

[@gbsandeep]

REpresentation State Transfer

[@faboukarykoulibaly2329]

VERY GOOD

[@Dziewana]

Watch at 1.25 speed, dont waste your time. Thank me later

[@motivationLab-NY]

I hope i am not being disrespectful. but why can't he explain it in layman's term…

[@howtodevelop6641]

Nice!

[@MrTeluguSongs]

Representational State Transfer

[@NorwayTracking]

Please leave my recommended

[@fanbondiK]

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

[@JinkProject]

is he wearing make-up??

[@carnagerpm]

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

[@ampix0]

Really poor volume.