Lecture 4.2: HTTP: Persistence, cookies, and caching

Loom

Learn to Loom How to Record Loom Blog Pricing

Srinivas Narayana・

over 4 years ago

303 views

1.2×

44 min⚡️55 min44 min37 min29 min26 min22 min18 min

😂

Anonymous

👍

Anonymous

😂

Anonymous

😂

Anonymous

👍

Anonymous

👍

Anonymous

👍

Anonymous

👍

Anonymous

😂

Anonymous

😂

😍

👍

Aamir

🙌

Anonymous

👍

Anonymous

Does having a persistent HTTP protocol mean the server is always on. If a server has no guarantee of being on is a non-persistent protocol better?

+1 other comment

When the main stress is on CDN network then how is it gonna act different compare to going without CDN?

+3 other comments

1.2×

44 min⚡️55 min44 min37 min29 min26 min22 min18 min

😂

Anonymous

👍

Anonymous

😂

Anonymous

😂

Anonymous

👍

Anonymous

👍

Anonymous

👍

Anonymous

👍

Anonymous

😂

Anonymous

😂

😍

👍

Aamir

🙌

Anonymous

👍

Anonymous

Does having a persistent HTTP protocol mean the server is always on. If a server has no guarantee of being on is a non-persistent protocol better?

+1 other comment

When the main stress is on CDN network then how is it gonna act different compare to going without CDN?

+3 other comments

joy

love

wow

yay

down

More reactions

3 Comments

Shrav

Feb 5, 2021

Does having a persistent HTTP protocol mean the server is always on. If a server has no guarantee of being on is a non-persistent protocol better?

Srinivas Narayana

Feb 8, 2021

Persistence of an HTTP connection is a property of the connection/session between the client and server. The hope is that the server can stay on through one session :-) If the server keeps failing within this time duration, it likely means that neither mechanism would really work well for the user.

Aamir

Mar 4, 2021

When the main stress is on CDN network then how is it gonna act different compare to going without CDN?

Srinivas Narayana

Mar 5, 2021

CDNs are like the "cloud providers" of web servers: they have lots of capacity (and expertise) in managing workloads at scale. Rather than, say, each enterprise working to scale their web service capacity, CDNs do it on behalf of multiple such enterprises.

Aamir

Mar 4, 2021

What is the purpose of CDN when we have LoadBalancing/NodeBalancing?

Srinivas Narayana

Mar 5, 2021

I assume by "LoadBalancing" you mean the ability of an enterprise (e.g., Rutgers) to balance load across its own deployments. If an enterprise is large enough in its footprint to do this on its own, it might not need a CDN. Large CDNs have hundreds or more points of presence all over the Internet. A large CDN is lmore ikely to have better load balancing capabilities across those points of presence, than a small enterprise with much fewer points of presence.