I'm only about 2 minutes and and already found myself talking to the screen as if you were really here with me. Thank you very much for doing this video sir, your explanations in analogies are on point.
Dave your vids and explanations are the very best I have found. I am a middle aged guy trying to get a basic understanding of web applications so I can try to communicate with a developer to build an app concept i have. i have watched several of your vids , always good. tks
Dave, I heard various explanations attempts in my company to that topic for explaining it to people who are less interested in technology but using Starbucks as an analogy was great. If I explain that to a client the next time I will just use your explanation... Everyone should get that :D
sessions are temporary. once the web browser is closed, all sessions expire. cookies last until expiry date is reached. data on server (in database) is not a session. but a cookie can contain a clientID which has corresponding data in a database record (which is not a session). sessions persist between web pages for the time they user is on your domain. but when they exit, the session is closed.
cookies were sent to client to track the sessions of the client so that server storage space can be maintained but if we maintain sessions there what is the use of it ?
ok, but if you log in to Netflix today using your iPhone cookie, and tomorrow on your macbook using your macbook cookie, does Netflix store just ONE session ID for both of those? You should put up a diagram of how multiple cookies can relate to one session ID. Also, when can session ID be changed? Logouts? Suspect activity? etc.... More detail please.
Sir, it might sound funny but I am a total noob when it comes to networking. My question is at 2:32 you said: Starbucks card is our identification on browser but it matches with "something " on Starbucks server , now what is this 'something' ? As there will be many cookies coming to the server at the same time.
Every request should be accompanied by a cookie, the identification. Think of Starbucks as just a huge server and can access some database once they see your cookie. Starbucks could be servicing millions of requests concurrently all with different cookies.
Sir, that means the cookies issued by the server to the browser are added to some sort of database and with every new request that the user makes , the cookie associated with the request is checked . If it matches then we are able to access further...is that so??
What you said is right, only thing being the cookies is always present in the client-side, which means it is issued by the browser to the server and not the other way around. And the 'something' that you were talking about, that was the session that is present on the server. The server would look up among all the sessions and pull the one which matches with the cookie.
I understand session and cookies but clicked your video out of curiosity. Your breakdown and analogies are very effective in explaining the subject.
Sessions and Cookies are what makes the http protocol stateful! Very well put - thank you. I will remember this. Great video by the way.
I copied that phrase from a Rails guide somewhere. It's a good phrase, haha
I'm only about 2 minutes and and already found myself talking to the screen as if you were really here with me. Thank you very much for doing this video sir, your explanations in analogies are on point.
Thank you! This explanation is the clearest I 've ever seen!!!
I am clear on session and cookies now. I really like the way you explain the fundamentals with examples. keep going.
huge respect for breaking it down in simple words. SALUTE!!!
This is the best explanation of cookies and sessions I have seen. Thank you Dave.
With that analogy, everything you have said about sessions and cookies are easy to understand. Thanks!
Best explanation I've seen online
man I was looking through UA-cam just to make sure I understood the logic but your video is amazing and now I'm certain!! thanks
cleanest explanation !
The moment you starts make that analogy, that's when I pressed the like button. Thanks man.
Excellent work!!!!
Damn bro, good job! That explanation was outstanding...
Awesome analogy and explanation
I really love your explanation and example.
wow. the video couldn't be better. it's just perfect. Thanks.
Man the explanation was mind-blowing. Awesome video.
I LOVE THE ANALOGY
Wooooww good analogy. Easy to understand. Thank you!
Thanks! @Dave
you've cleared all my doubts on basic understanding of sessions and cookies. BTW, the example you took is really cool! =D
Man was this ever helpful. First taste on this subject and I got buried in the Flask doc.s....now I see what the hell they're gonna do. ThanksDave!
love the analogies you use in explaining things. subscribed!!!
Great analogy. I understand cookies and sessions now.
Wow it's very cool. And Turkish subtitle is extremely native. ( Çok iyi çevirmişsin teşekkürler :) )
Theres nothing like a well explained analogy.
Really helpful video to understand cookies and sessions with real time example.
Thank you.
crystal clear explanation, thanks.
watching this made things so clear for me , Thanks Dave!
The analogy makes perfect sense :). Thanks bro
OUTSTANDING EXPLANATION!!!!! Thank you!
Amazing analogy for the cookie
Dave your vids and explanations are the very best I have found. I am a middle aged guy trying to get a basic understanding of web applications so I can try to communicate with a developer to build an app concept i have. i have watched several of your vids , always good. tks
You explained it soo well. Thanks man.
love this best explanation
Hello. Thanks for the video. So as I understood sessions are like super cookies, which can store much more info compared with simple cookies?
Thank you Dave, these videos are really informative!
Fantastic
You're brilliant man. Keep up the good work.
Great work👍
Crystal Clear, thanks mate
thanks for your amazing explanation!
Beautifully done. i actually did know what was session n cookie, but your video made the concepts so clear.
if u understand this sentence then you nailed it to learn cookies and session... ""every HTTP request without cookies and session is stateless""
I love ur analogy, Could u tell me what's a session in analogy? Thank you so much!
Very clear explanation. Thank you!.
Best explanation bro. Thanks.
that was a way better explanation than obnoxious linus tech tips version
Great explanation!
great work , really helpful , thanks dave , looking forward for more vids
best explanation!!!thanks alot!!! great analogies!!!very easy to understand!!!
You are a god engineer, you know how to explain bro.....Just brillant
Dave, I heard various explanations attempts in my company to that topic for explaining it to people who are less interested in technology but using Starbucks as an analogy was great. If I explain that to a client the next time I will just use your explanation... Everyone should get that :D
sessions are temporary. once the web browser is closed, all sessions expire. cookies last until expiry date is reached. data on server (in database) is not a session. but a cookie can contain a clientID which has corresponding data in a database record (which is not a session). sessions persist between web pages for the time they user is on your domain. but when they exit, the session is closed.
finally find comment mention this.
Excellent video, thanks 🙂
Loved the analogy
Excellent analogy! Thanks bud.
thnx man... u were more clear den my faculty members... thanx alot
can you make a video about internet layer and function of each layer. i still feel confuse about it
Really good example!!!
You've got a new subscriber. Great explanation in short time.
Cool video man. Thank you.
You're doing God's work. Thank you sir!
a great video and the analogy was super useful
cookies were sent to client to track the sessions of the client so that server storage space can be maintained but if we maintain sessions there what is the use of it ?
Dave, Question how do you structure your week. When do you work and when do you get you time?
best explanation ever
thank you very much, info was awesome, i now understand, subbed
A great explanation to the topic. I knew it before but this really helped me understand it better from a real life example. Cheers..
excelent top class
amazing explanation, thanks
Amazing explanation!
thank you . well explaned !
Thank you for this Video it helped me very much to more understand the difference between sessions and cookies 😊👍
Thank you, excellent analogy!
Thanks from my heart ❤️ ♥️ 💜 💙 , Finally I understood what are the difference.
Very well analogy sir
I really enjoyed the detailed explanation. Thanks alot
great analogies! thanks for the video!
l like l how l watched this 3 years ago, and here l'm again refreshing the infos
well explained btw, thanks
thank you, great explanation!
Thank you so much.
Really it was very useful.
thanks a lot.
explained the concept really well.
Awesome videos. Always easy to understand and informative. Thanks!
I give a like and I subscribe because of your goddamn amazing work.
Very good
ok, but if you log in to Netflix today using your iPhone cookie, and tomorrow on your macbook using your macbook cookie, does Netflix store just ONE session ID for both of those? You should put up a diagram of how multiple cookies can relate to one session ID. Also, when can session ID be changed? Logouts? Suspect activity? etc.... More detail please.
So complicated, yet so simple. I appreciate your time in making this vid. They should've just called them "Cards". lol "Cookies" is cool though...
Great Explanation
thank you very much good analogy.
Thank you man very helpful !!
Thank you very much, it was very enlightening.
Cool video man!
Thanks, man!
Wow so clear
Good vid man, solid explanations.
Great explanation!! Thanks.
Sir, it might sound funny but I am a total noob when it comes to networking.
My question is at 2:32 you said:
Starbucks card is our identification on browser but it matches with "something " on Starbucks server , now what is this 'something' ?
As there will be many cookies coming to the server at the same time.
Every request should be accompanied by a cookie, the identification. Think of Starbucks as just a huge server and can access some database once they see your cookie. Starbucks could be servicing millions of requests concurrently all with different cookies.
Sir, that means the cookies issued by the server to the browser are added to some sort of database and with every new request that the user makes , the cookie associated with the request is checked . If it matches then we are able to access further...is that so??
What you said is right, only thing being the cookies is always present in the client-side, which means it is issued by the browser to the server and not the other way around. And the 'something' that you were talking about, that was the session that is present on the server. The server would look up among all the sessions and pull the one which matches with the cookie.
Great explanation, your new filming location looks much better :)
Nice, understood it very well.