Skip to content

Packets aren't related to concurrent transactions #41479

@shivangthakur-007

Description

@shivangthakur-007

MDN URL

https://developer.mozilla.org/en-US/docs/Learn_web_development/Getting_started/Web_standards/How_the_web_works

What specific section or headline is this issue about?

packet explained

What information was incorrect, unhelpful, or incomplete?

Packets explained
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, but most significantly:

They are sometimes dropped or corrupted and, when this happens, it's quicker and easier to replace small chunks than entire files.
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 would make the web very inefficient and not much fun to use.

What did you expect to see?

In this explain about packet in last line it depicts as only one user could download at a time is the example of problem of circuit switching but in packet switching at a time a client can get the same page or chunks and others also due to server serves as separate transaction. and with the help of packet (small packet) we can overcome from the problem of network traffic.

Can you illustrate me whether I am wrong or right about this.

Do you have any supporting links, references, or citations?

No response

Do you have anything more you want to share?

No response

MDN metadata

Page report details

Metadata

Metadata

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions