Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Comments on What is REST and how different it is from HTTP?

Post

What is REST and how different it is from HTTP? [closed]

+2
−2

Closed as too generic by Alexei‭ on Feb 16, 2021 at 06:56

This post contains multiple questions or has many possible indistinguishable correct answers or requires extraordinary long answers.

This question was closed; new answers can no longer be added. Users with the reopen privilege may vote to reopen this question if it has been improved or closed incorrectly.

Based on my understanding HTTP is something client and server speak in, I mean it is like a language for a server and client to communicate(not exactly a programming language). Then how to understand REST? Please provide some analogy and explain.

History
Why does this post require moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

General comments (4 comments)
General comments
FractionalRadix‭ wrote about 3 years ago

I feel this question is too broad. HTTP is a protocol, strictly meant for the web. It has a formal specification. REST is an architecture - it's a set of design principles, and if any application follows these principles, it can call itself RESTful. But unlike HTTP, there's nothing formal about it - no specification, no comittees.

r~~‭ wrote about 3 years ago

I agree; you should probably give https://en.wikipedia.org/wiki/Representational_state_transfer a read and then ask some more specific questions about REST if you have them.

meriton‭ wrote about 3 years ago · edited about 3 years ago

In addition, the usual caveat for all terminology questions applies: Different people may associate a different meaning with this word. There is no universally accepted definition: To some, REST means the architectural style in Fieldings dissertation. To others, it simply means they sometimes use HTTP verbs other than POST. Or anything in between. That's why you should ask whoever is using the term rather than strangers on the internet ;-)

Alexei‭ wrote about 3 years ago

I also think this question is too general as it is right now and I agree with the reasons stated in the other comments.