2.2 The Web and HTTP part 2

Video presentation: Computer Networks and the Internet.
2.2 The Web and HTTP (part 2). Web caches, Conditional GET, HTTP/2
Computer networks class.
Jim Kurose
Textbook reading: Section 2.2, Computer Networking: a Top-Down Approach (8th edition), J.F. Kurose, K.W. Ross, Pearson, 2020.
See gaia.cs.umass.edu/kurose_ross for more open student resources.

[@karanpreetsingh5966]

Totally the inspiration I needed in my life.

[@starless9]

Anyone know if this or an equivalent course is offered on a MOOC platform?
Just to get a certification for completing the material.

[@sandboom_7260]

Will the web cache server send a head request every time to the origin server to get if it has gotten modified whenever i access that site

[@varshashiremath1431]

Just amazing

[@pythonicd1239]

8:29 how do we get the 0.01 sec queueing delay? And how do we take the average data rate to be L/R. In the sense that if the link capacity is 1.54Mbps, but it needs to be utilised by both the institutional router and the public internet router to load bits onto the link. So does that means that the sums of the rates at which btoh the routers are loading bits onto the link shouldn't exceed 1.54 Mbps? So how do we know that the browsers receive requests the rate at which they send them? Like 15 requests are sent in one second, that is 15*L packets in one second.

[@daeunlee5921]

Hello at the 4:50ish mark can you explain how you did your math?

[@alessandrovecchi5147]

1.50/1.54 and 1.50M/1G

[@devmahad]

Performance:
Web caches,
Conditional GET,
HTTP/2 HTTP/3

[@jatoxo]

I'm confuzzled by all the splitting that's happening in every layer and why it has to happen
Currently you can have an IP packet containing a partial TCP packet which contains part of an HTTP/2 packet which contains part of the HTTP Object
Why does every layer need to split it's data up, you'd think that one single layer should be responsible for this

[@user-qe3qm6np9b]

still wanna know?

[@user-hp1oz4ul6w]

WAH DADA WAH

[@aviChillin]

At 2:55 , “no-cache” means the response can be stored in caches, but the response must be validated with the origin server before each reuse. It does not mean "don't cache at all."

[@shayfabrizio3107]

Poggers Keanu

[@klevisimeri607]

🧠

[@alirizvi3506]

u r so bad in explaining numericals, btw thanks for the playlist!

[@kokyoongee1294]

He has done an incredible job in explaining the concepts. You should try to find your own knowledge gap, if you don't understand it.

[@graysonparker1593]

If you cant find and understand percentages or do basic multiplication and addition on your own that sounds like a you problem...

[@me1sTerweeD]

Division and %s are part of high school math