The QUIC Protocol, HTTP3, and How HTTP Has Evolved

preview_player
Показать описание
In this video, I dicuss how HTTP has evolved over the years and explain the QUIC protocol and HTTP3.

---------------------------------------------------------------------------------------------------------------------------------------------------------------

HOW TO GET IN CONTACT WITH ME

🐦 X (Formerly Twitter): @TheDataDaddi

Feel free to connect with me on X (Formerly Twitter) or shoot me an email for any inquiries, questions, collaborations, or just to say hello! 👋

HOW TO SUPPORT MY CHANNEL

If you found this content useful, please consider buying me a coffee at the link below. This goes a long way in helping me through grad school and allows me to continue making the best content possible.

Buy Me a Coffee

As a cryptocurrency enthusiast, I warmly welcome donations in crypto. If you're inclined to support my work this way, please feel free to use the following addresses:

Bitcoin (BTC) Address: bc1q3hh904l4uttmge6p58kjhrw4v9clnc6ec0jns7
Ethereum (ETH) Address: 0x733471ED0A46a317A10bf5ea71b399151A4bd6BE

Should you prefer to donate in a cryptocurrency other than Bitcoin or Ethereum, please don't hesitate to reach out, and I'll provide you with the appropriate wallet address.

Thanks for your support!
Рекомендации по теме
Комментарии
Автор

The thumbnail states how passionate and organized your efforts and knowledge. Kudos.

ShivaShaktiOnMoon
Автор

The way you explain is quite awesome.

Need more please.

1.More about packet flow of Quic
2. Re-transmit handling in Quic
3. Congestion control in Quic
4. Connection reliability in QUIC

pranavsingh
Автор

Because QUIC is disassembled at the app layer, it's impossible for a company gateway to sense or block undesirable content be that ads, inappropriate content, or known sources of malware.

QUIC now forces end-point solutions to be able to catch content elements at the app layer.

This really makes IDS/IPS much more difficult.

lohphat
Автор

most consise and organised explaination I've seen on this topic

hemant_pande
Автор

you did a good job explaining this, thank u :)

abdallahelhdad
Автор

Great Video, thanks for putting i so much efforts and making it simpler

Ranjeet_
Автор

Nice video! Thank you for the explanation!
On the http/2 vs quic diagram you have “udp connections”. But it’s irrelevant to the udp, cause on the lower lever udp doesn’t establish connections.

useruser
Автор

Hands up who had to look up the word inchoate!

cthutu
Автор

@TheDataDaddi - your slide is wrong. Client-initiated streams are even, NOT odd. This is according to the RFC 9000

cthutu
Автор

Please make a deep dive Video for QUIC .

I have a query: What if first packet is lost. UDP won't re-transmit so Server will never get it and Client will keep waiting time-out and then send again ?

pranavsingh
Автор

Can quic protocol be used between Microservices ?

Any Service Mesh supports QUICK protocol? If so that would make the network faster right?

satish
Автор

As far as I know. AdGuard is the only that has this.

truesonic
Автор

There's no such thing as UDP Connection...

_general_error
Автор

'Server load spike' - not well explained.

wuzhai
visit shbcf.ru