Intro to REST (aka. What Is REST Anyway?)

[@ec4307]

watch this at 1.5 speed and thank me later.

[@greekstraycats]

+Eugene Connor Thanks a lot - 1.25 did it for me :-)

[@Sam-cx4du]

+Eugene Connor Thanks :)

[@elnino204]

+Eugene Connor I love you. I almost shut this off. It's a great video but painful to watch at 1x

[@machariamaguta5465]

+Eugene Connor Thank you! Ahahaha!

[@tedaarks]

+Eugene Connor Thank you

[@MatthysduToit]

You really read that presentation well!

[@de_leben]

after watching, i need a rest

[@siham3801]

+Kun-Yao Wang Me too :D

[@vinodcs80]

Old video but still very relevant and useful. One of the best explanations on web

[@skdiamond]

I've watched a few KZbin videos on REST. In spite of the many negative comments I found this video to be useful. The author does a good job of explaining the overall principles of REST

[@fernandolima8154]

I really don't get why there is so much criticism. The guy is investing his time to freely provide some useful knowledge. If you didn't enjoy the pace or if you think you could do it better, just keep it to yourself and do your own. But since you got to this page is really because you searched for an introduction information about REST meaning you don't have the knowledge to do any better.

[@anujp52]

Wow. you made this back in 2012 when REST was still in RESTing "state' compared to now! Well done.

[@wealtylife5518]

Okey, smart people, first time I watched this video two month ago just 2-3 minute and closed it. because I found it awful. Now I tried to catch what author is meaning, I watched until the end. I found it #1 imformative video ever on REST. Please, try again who found it not useful.

[@mantasjoniskis]

After watching this video 10 years later and reading though the comment I've concluded that majority of the negative comments are invalid. I rest my case.

[@DrewMullen]

"people are find it easier..." Thanks for putting something like this together, author. But, did you practice this at all before posting? The pausing lack of examples makes the concepts inaccessible (dull). If you took the time to redo the video (a 2nd or 3rd time), I'm sure the quality would be much higher!

[@daithisad]

This is a great video. Really helped in reinforcing what I thought I understood about REST concepts. Thanks Todd.

[@DanGolag]

Saying "For example" doesn't actually count as providing an example. "Logic, as in executables, can be transferred as a representation to the client." I'm sure that's perfectly clear to people who already know "What is REST anyway" to me it was gibberish.

[@TheCovenantChild]

Check this out: en.wikipedia.org/wiki/Code_on_demand. It gave me some clarity

[@Crasshopperrr]

Much more confused after watching this than I was before watching it.

[@Johanna77777-z]

He doesn't really say much. Just rest your mind and view this as an introduction to how to think and practical information may come later

[@ashishverma-mj1kl]

kzbin.info/www/bejne/iYWbiaughLl8qck

[@emilionavarro616]

This an education video to focus on content, not on the style of the presenter. If you do that you get the most of it.

[@siavoshkasravi398]

If you ask me what REST is, I would say it is the simplest way a client can get or set data from or to a server using HTTP.

[@crogersdev]

Around 6:20, you mention 'GET' in the RESTful example. Can you explain in more detail how the GET operation figures in to REST when REST isn't supposed to be verb based?

[@shann.s.4996]

read about http pls

[@wanghongbin99]

I think it is good Because the concepts in it are clear.

[@rossdiaz]

In this video, Todd Frederich looks like the actor John Corbett auditioning for the role of Han Solo

[@adamtak3128]

I was going to watch this but after reading the comments I suppose I'll save my time and skip.

[@OsirisPL]

How not to explain a technology: dry theory, no examples, lots of bullet points

[@VinnyDrysdale]

Please correct me if I'm wrong, but it's my understanding that, when the concept was conceived, the "State Transfer" was meant to happen when the client acted upon what was returned from the server. For example, if the an HTML page is returned, it will contain hyperlinks the client (via a user click) can then use to transfer to its next state.

[@moaazelsayed]

after 6 years, yes that's right

[@yas2ne19]

great vid bro, thanks!

[@segmentationfaulter]

The video assumes you already know a lot about REST architecture and examples are very abstract too.

[@MePeterNicholls]

These needed more examples, as the other guy said. I couldnt take in any of this as I couldn't see what you were talking about.

[@alkodjdjd]

in this video we will introduce REST. why? because it's cool. how? through this very video you are watching. and so we shall start now ok? what is rest? well, rest is... (switching to other youtube channel)

[@sadamps]

You look like Bryan Ferry. The start of the video reminds me of that Jealous Guy music video.

[@omarahmed51512]

thanks for explaining ! subscribed

[@JimSowers]

If you want to be effective: provide EXAMPLES. Not just "nouns v verbs", but actual examples of actual API calls of each kind.

[@RajatRastogi85]

how does authentication would happen if server is not keeping any state of the client ? Any client can call any method ?

[@suhlabs]

The video hangs at 10:46. Why?

[@Newbyte]

Something wrong on your end probably.

[@prashantsharma6870]

Very Helpful video.

[@mohammedabulsoud517]

What doe's it mean stateless. I don't understand anything.

[@JosephNogueras]

+Mohammed Abulsoud Means there is no state, the state is carried within the client and not the server

[@JosephNogueras]

+Mohammed Abulsoud ok, by stateless means is a REST constraint that restricts a web server from holding on to any client-specific state information, which helps it support more clients. Got this from the book REST API Design Rulebook by Mark Masse

[@mohammedabulsoud517]

you mean it's just an api call. The client call the api and the other side will always reply to it's request. so for example if your want to know the number of likes a post gained in facebook you may create a call (http request) to some resource. I'm sorry for asking this but what kind of states could the server wait from a client in order to complete a previous request. because there's always a handshake occurs between client and server at every request imitated need to be completed before the transfer occurs which I see it as a state called handshaking.

[@JosephNogueras]

+Mohammed Abulsoud I believe the server must be stateless to be considered RESTFUL

[@JosephNogueras]

+Joseph Nogueras “keep the application state on the client.” Encode application state into URIs, and include those URIs into representations via links. Got this from RESTful Web Services Cookbook

[@jshaker2007]

cmon guys, chill. u r not paying his bills. he is doing this to help others selflessly.

[@olivier2553]

http is stateless, that's a great discovery!

[@anmolsworld8038]

Thank You for nice explanation

[@khafanus]

what is its definition?

[@janvierma]

I haven't shot myself yet. How come?

[@matrixmodulator]

Pop filter please :)

[@shahryarsaljoughi6073]

there is a typo in the first slide : this is conStraint NOT contraint

[@amarnath12321]

simply awesome...!

[@eternalwanderer3785]

Despite understanding most of what he's saying, I think he should review his presentation before recording it. Totally reminds me of my profs in university and it's confusing as f**k when he's more worried about using proper terminology than actually using examples and simple vocabulary. I'm trying to learn here, i don't give a f**k how smart you sound. "Code on Demand is unique as a Restful architecture constraint BECAUSE it is the only optional constraint" ... WTF did he just say??...

[@energale]

this helped a lot to understand the concepts

[@rishabhsethi29]

Great. Now I know less about Restful API after watching this.

[@bipulkalita7661]

I found a line somewhere _"REST is based on the idea that you should send data but also information on how to consume the data."_

[@gedunsworth3191]

This is a terrible video. I normally don't comment because people do their best but this makes this relatively simple process seem oh so difficult.

[@Oswee]

Totally agree with this! Explanation is terribly difficult.

[@caseyspaulding]

Thanks

[@Merlin5by5]

SO, the REST architecture implies the server should be able to respond to any blind request at any blind point in Web site position, from any client, at any point in time? Seriously, doesn't that sound just a bit ambitious?

[@shreyas176]

Authentication is done between. so blindly server wouldn't respond you requests

[@devdeeds]

Good explanation. Thank you!

[@farhanakram9188]

Thanks mate

[@rathisoft]

Very informative. Thanks.

[@auspicious99]

Good coverage of the concepts, but unfortunately, not presented in the best way for learners. For example, it lacks examples ..

[@loknath9]

very useful...

[@delly8359]

To many ressources

[@shahin7511-yt]

Wow; awesome......... Thanks a lot :)

[@AbelChipepe]

Sir. With all due respect you are having hard time explaining. I do understand the need for Rasp API tutorial but this way we are going back to nothing. Destruction instead of construction. At least you tried.

[@abdulabu3839]

good

[@bobmoore8909]

Using acronyms makes this really difficult to follow. I through about two minutes and instead of googling every acronym I'm going to find a new video. Frustrating.

[@tafadzwaoliviamufundisi8560]

The team

[@PerryCodes]

Really in need of a better microphone!!

[@takfuruya]

Too abstract. Need examples.

[@rexdamage]

Slow, boring and confusing. Like I'm watching a documentary about mating practices of deep water slugs.

[@bogdand6129]

Thank you for the video but the content quality is just awful.

[@killlion]

excellent video, thanks a lot!

[@yomamasofat413]

kinda hard for a beginner to understand

[@siccckhead]

I didnt watched the full video coz i got bored. The tutorial is more like strick definitions which are always boring without good examples. Sorry to say but didnt enjoy the tutorial!!

[@uhmgawa1435]

A great video to remove 19:06 from your life. But I doubt you'll stay awaye that long. Less exciting than watching paint dry.

[@codersince007]

Don't record a video in your bathroom!

[@kalyanasundramkalyanasundr4736]

ச

[@jaderzanotti]

TL;DR:

[@bitkahuna]

that's tenets, not tenants. DOH!

[@MiguelangelFernandez82]

I'd just say its too slow paced

[@jan_hamara]

I mean seriously, this must be a prime example of how NOT to teach (REST or anything else)... IS THIS SUPPOSED TO BE "INTRO", U KIDDING ME?

[@renayrenayrenayao]

Yes, the video is boring. The most important thing is you didn't provide any example at all. I also doubt that you understand what Rest is all about because it seems to me that you were reading a note to us. You weren't explaining and i knew it from your eyes movements.

[@rayrack5416]

Powerpoint vomit

[@campyc40]

Horrible.

[@wtwrva]

Terrible!