Learn Web3 in 100 Days - Day 2: What are the Browsers and Servers

Do you ever wonder how the browser actually works? Well, if you do, then follow my thoughts. Even if you don’t, come join my thoughts too.

TL;DR

What is the Browser

What is the Server

HTTP

How It Matters in Web3

Distinguished Between Web2 to Web3

What is the Browser

The browser is a communication tool to speak with the web server. It sends requests to try to access information stored in the web server and download them so it can display information to users.    

Thinking about you walking into the library. The browser is a service center and you are about to request a librarian to help you to find a book.

What is the Server    

The server is like a library that stores all sorts of books. Instead of books, the server stores information data that the website designed. If you want to browse the website, you need the browser to send a request to the web server with encryption messages to allow you to download information data from the server.   

HTTP

Hypertext Transfer Protocol is a standard language that browsers talk to servers. Thinking about HTTP as the book name, so that if you want to borrow a book in the library, a librarian can help you to find it from the library.

How It Matters in Web3

Think about a wallet that is like a browser and you will find your crypto information in the wallet with the total amounts you have and other key information. The server is like nodes of the blockchain. HTTP is more like a wallet function that you are about to execute or a smart contract that you interact with. When you send your crypto to another address you intend to do so, the wallet then passes information into the blockchain with a block that all nodes of miners will compete to find a better computing power that helps to validate the transaction and go through previous blocks. Until the transaction has been validated, it will add to another block and be posted on the blockchain to confirm the transaction. 

Distinguished Between Web2 to Web3 

From web2, the browser only approaches a particular server to request information from it while in Web3, the transaction is posted on the server where miners come to compete and validate the result of the approval of such transaction. The prior example is a conversion and the latter example is a diversion.

In conclusion

You can now understand how browser and server interact while how wallet, miners, and blockchain works.  

The next topic I will touch on is the 404 error page and blockchain error transaction.