Day89 of #100DaysOfCode

Day89 of #100DaysOfCode

Hii folks 🙌

Today I will be starting a new pathway in which we will learn about HTTP and REST.

Unit 4: Internet

Pathway 2: Get and Display Data

Introduction to HTTP/REST

HTTP is the protocol that allows for sending documents back and forth on the web. A protocol is a set of rules that determines which messages can be exchanged, and which messages are appropriate replies to others. Another common protocol is POP3, which you might use to fetch an email on your hard disk.

In HTTP, there are two different roles: server and client. In general, the client always initiates the conversation; the server replies. HTTP is text based; that is, messages are essentially bits of text, although the message body can also contain other media. Text usage makes it easy to monitor an HTTP exchange.

REST is a simple way to organize interactions between independent systems. It’s been growing in popularity since 2005, and it inspires the design of services such as the Twitter API. This is due to the fact that REST allows you to interact with minimal overhead with clients as diverse as mobile phones and other websites. In theory, REST is not tied to the web, but it’s almost always implemented as such and was inspired by HTTP. As a result, REST can be used wherever HTTP can.

That is all for Day89 ✅

Thanks for reading, See you tomorrow!




Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Building Satoshis Games #1

Stored procedure with output parameters

Azure DevOps Training Day-2

Your stylesheets need methodology!

NG19. Non-alternating ditransitives


Serverless idempotency with Azure Functions — Issue #94

Buyer personas

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Kushagra Kesav

Kushagra Kesav

More from Medium

Day62 of #100DaysOfCode

Day77 of #100DaysOfCode

Day51 of #100DaysOfCode

Day57 of #100DaysOfCode