the comments here are like a blast of great Amazon reviews. And you can tell by the sir. I appreciate the video. Would not be able to follow along without the animated text though.
thanks I read a few articles about http method, I dont really understand idempotent , PUT POST are different http method, but its really up to the restful code who make its idempotent? let's say HTTP Post is to CREATE, but backend code can check whether the record exists or not then do create or update accordingly? PUT is to update, backend code can create a new record in Database and keep creating new one each PUT request received?
I am young java junior developer with no experience, and I am looking for a non paid intership. Let me know is there any company which is looking for interns.
Hi bro, I want to know why http sent as initial request if it is not secure also.? Why not initial request sent as https..? Please bro reply to this I have a work based on this topic please help me.
Of course, when these terms were being created, more thoughtful nomenclature would have avoided wasted hours of confusion. Great explanation though. Thank you.
If it will update the resource, without even giving a second thought it should be PUT not POST. Use POST when: You are creating a new resource Use POST when- You are going to update the complete resource (notice, I have used complete resource, again if you are going to update every information of a record/resource use PUT, if you want to partially update meaning only the marks of a student it should be PATCH). I hope it makes sense
@@RenuRawat - I think you are missing my point. If you are updating a resource with someone's new email address, then yes, I see why you would use a PUT. But if you are updating someone's bank balance by $10, then it is not idempotent because you could end up updating the bank balance by $20 or $30 if you resubmit the request 2 or 3 times. Don't you want the browser to warn the person that the transaction has already been submitted?
I dont agree with "Post" being idempotent... If we are sending "post" and it is creating a record everytime then I guess validation is not rightly placed in the code.
i have watch your video yesterday i dint understand a lot but today once again i watch your video and i understand whole thing easily great explanation in easy not too much confusing
Wow!!!! What a great explanation, Sir!!!! As simplified as it can be!!
😒😒😂
Been using Post both for post and Put 😂
Hello Sir,your explanation is always on point,great video!!
Wow!! Great explaination!! N this http based question will be asked for nearly 8 to 10 marks.... In my upcoming computer networking exam.... Tq...
what an explanation....when ever I get confused I always prefer your tutorials
Do you know how Awesome you are? Loved the explanation!
Request: Please make tutorials on JavaScript advance concepts(callbackHell(), promises() etc.)
one of the finest explanation ever got
Please, help me out.
I want to know, how @nickatnyte records his clash royale videos for RUclips...
Which software he uses and what else....
OBS
Worthy for watching this. Helpfull , understandable
Wow, very clear explanation. Other tutors made it look like rocket science
the comments here are like a blast of great Amazon reviews. And you can tell by the sir. I appreciate the video. Would not be able to follow along without the animated text though.
Suggest any book to learn Java from very beginning, I mean learn so basic concepts...
awesome explanation..!! i have been searching for this kind of answer from a long time, but with your explanation the search has ended
thanks I read a few articles about http method, I dont really understand idempotent , PUT POST are different http method, but its really up to the restful code who make its idempotent? let's say HTTP Post is to CREATE, but backend code can check whether the record exists or not then do create or update accordingly? PUT is to update, backend code can create a new record in Database and keep creating new one each PUT request received?
I have tried, network engineer perspective
Thank you very much for this video! It was very clear and I learnt a lot :)
A very important concept.Very well explained thanks.
You exposed all the basics of HTTP Methods in 5.5 minutes, it requires great clarity of concepts to do this and you did it. Thank you so much
Thank you REDDY, nice explaination.
Great simple explanation of put versus post!
my favorite tutor always!!!
Good video....would have been better if patch was covered as it is asked in interviews
I am young java junior developer with no experience, and I am looking for a non paid intership. Let me know is there any company which is looking for interns.
Thanks man! Your approach is very clear to understand.
thanks for the video. But why so many jump shots, i cant help but get a bit distracted with it.
Super bro ,chala Baga explain chesav 🤝
Such clear explanation. Thank you so much!!!!
i love your way of explanation...i wonder about you... you are my roll model sir....
Thank you for clarifying my year old doubt.
Hi bro,
I want to know why http sent as initial request if it is not secure also.?
Why not initial request sent as https..?
Please bro reply to this I have a work based on this topic please help me.
PUT the server to store a web page
POST means updating the web page
Sir provide one example of working with REST
tq sir ....clean and clear explenation sir.....
Of course, when these terms were being created, more thoughtful nomenclature would have avoided wasted hours of confusion. Great explanation though. Thank you.
Taklu1, bald2, skinny bald3, shinny taklu4🤗
Nice sir 👍👏😊
HI Naveen, can you please explain PATCH and Difference between PUT and PATCH
Thank you.
What if you are updating a resource by adding 10 to a value. Is that a POST or a PUT because it will update a resource but is not idempotent.
If it will update the resource, without even giving a second thought it should be PUT not POST.
Use POST when: You are creating a new resource
Use POST when- You are going to update the complete resource (notice, I have used complete resource, again if you are going to update every information of a record/resource use PUT, if you want to partially update meaning only the marks of a student it should be PATCH).
I hope it makes sense
@@RenuRawat - I think you are missing my point. If you are updating a resource with someone's new email address, then yes, I see why you would use a PUT. But if you are updating someone's bank balance by $10, then it is not idempotent because you could end up updating the bank balance by $20 or $30 if you resubmit the request 2 or 3 times.
Don't you want the browser to warn the person that the transaction has already been submitted?
sir please make a course on computer networking ...idk how but your 2 min on client server worth more than 2 hours of my googling
I dont agree with "Post" being idempotent... If we are sending "post" and it is creating a record everytime then I guess validation is not rightly placed in the code.
This is very clear now
Can't i achieve GET command work using POST command?
Why is PUT unsafe?
We are updating that data only for ourself, not for every user in that accesses those files in the server, right ?
Amazing video sir!
POST is not unsafe method..
post is non idempotent and put is idempotent
Why are you talking about aliens hahaha
Explanation good, but please try slowly to explain the content clearly
Thank you! This greatly clarified y confusion about PUT and POST in a very comprehensive way.
you're the man!!! new sub here
This is the part of which playlist ?
How post is unsafe and get is safe
superb explanation sir
PUT and POST , using both we can create and update records. Can you please elaborate in detail that when exactly to use which one.?
Thank you so much sir
Well had a confusion on these things..But now i have clear view on these... Thanks
Superb sirrrrr❤️❤️❤️❤️
helpful video to understand all method very easily
I'm subscribing because I like how you explained this. I'm grateful.
Thanks Navin..!! you're the best!
nicely explained
Java brain copy
Your videos and examples really help alot. Great explanations
Hi navin....good video about http methods...but you did not covered http.update which is also used nowadays
It's really informative and I am.happy to see you to use your native language Telugu to name your channel
realy AM enjoy
Gud explanation sir..explain abt various http status code
👌...very helpful video sir...
Thanks, Reddy. Nice explanation.
Thank you
Taklu1 taklu2 taklu3 taklu4
thanks
Thank u
Thank you so much sir.this will help me to hack your e-mail account and also your youtube channel.😈
i have watch your video yesterday i dint understand a lot but today once again i watch your video and i understand whole thing easily
great explanation in easy not too much confusing
Sir,Please make a video on how to explain project architecture ..for interview purpose.....for Exp...People...
excellent explanation sir 🤩
Can you help in explaining PATCH too?
taklu
Please make video on operating systems and design patterns
sir just Respect you :)
its very clear sir, thank you
then what is patch??
👌👌👌👌👌👌👌👌✅
Did this guy call me an alien?
Bro Make a video on GraphQL
Nice explanation.tq
Bang on and in just 5 minutes. Thanks
Wow just 5 min but Chrystal clear!
sir kindly correct GET is also Idempotent
👍👍
superb Explanation
You lecture are awesome please upload the detail of Rest method.
Your explaination are really mind blowing
can you please make video on request module and json module
Best video I had ever seen regarding this topic
You are the best!!!!
Awesome explanation
This is just outstanding.
Extremely good
you made it crystal clear
thanks