Explore >> Select a destination
|
You are here 
|
cookie.engineer | ||
| | | | |
scorpil.com
|
|
| | | | | Short history of HTTP protocol | |
| | | | |
lenholgate.com
|
|
| | | | | [AI summary] The author critiques the design of the WebSockets protocol, arguing that despite its claim to be message-based, its fragmentation features effectively turn it into a stream-based protocol that forces manual buffering and complicates application layer design. | |
| | | | |
sookocheff.com
|
|
| | | | | Note: To make this easier to read (and write), h1 may be used in place of HTTP/1, and h2 may used in place of HTTP/2. HTTP/1 has a long and storied history. Originally developed as a sixty page specification documented in RFC 1945, it was designed to handle text-based pages that leverage hypermedia to connect documents to each other. Typical web pages would kilobytes of data. For example, the first web page was a simple text file with web links to other text documents. Now, the web is made up of media-rich sites containing images, scripts, stylesheets, fonts, and more. The size of a typical web page is measured in megabytes rather than kilobytes, and the number of requests required to assemble a full page can be over one hundred. The reality of how web pages... | |
| | | | |
ivaylopavlov.com
|
|
| | | On my quest to make shorter videos on programming fundamentals, I'm kicking this initiative with a video explaining the mechanics of compiled and interpreted programming languages and the trade-offs associated with each. The presentation inside Read more... | ||
