Skip to content

Commit

Permalink
Fix: packets goes _between_ server and client (mdn#30321)
Browse files Browse the repository at this point in the history
* Update index.md

The statement indicates that packets are only sent to the client. Yet, servers also receive packets from clients. So I changed some content of line 69 from "sent from server to client" to "transfered between the client and server"

* Update files/en-us/learn/getting_started_with_the_web/how_the_web_works/index.md

---------

Co-authored-by: Hamish Willee <hamishwillee@gmail.com>
  • Loading branch information
Cybersharph and hamishwillee committed Nov 17, 2023
1 parent 675d6fa commit d451eec
Showing 1 changed file with 1 addition and 1 deletion.
Original file line number Diff line number Diff line change
Expand Up @@ -66,7 +66,7 @@ Websites can be reached directly via their IP addresses. You can use a [DNS look

## Packets explained

Earlier we used the term "packets" to describe the format in which the data is sent from server to client. What do we mean here? Basically, when data is sent across the web, it is sent in thousands of small chunks. There are multiple reasons why data is sent in small packets. They are sometimes dropped or corrupted, and it's easier to replace small chunks when this happens. Additionally, the packets can be routed along different paths, making the exchange faster and allowing many different users to download the same website at the same time. If each website was sent as a single big chunk, only one user could download it at a time, which obviously would make the web very inefficient and not much fun to use.
Earlier we used the term "packets" to describe the format in which the data is transferred between the client and server. What do we mean here? Basically, when data is sent across the web, it is sent in thousands of small chunks. There are multiple reasons why data is sent in small packets. They are sometimes dropped or corrupted, and it's easier to replace small chunks when this happens. Additionally, the packets can be routed along different paths, making the exchange faster and allowing many different users to download the same website at the same time. If each website was sent as a single big chunk, only one user could download it at a time, which obviously would make the web very inefficient and not much fun to use.

## See also

Expand Down

0 comments on commit d451eec

Please sign in to comment.