News for hackers. Stuff that matters.
Re:What is the space overhead of Base64 encoding? by _petronius on Thursday January 31, 2019 @04:36AM (#19043609)
For the first load of the page, sure. But if you're embedding HTML and CSS, then you can't cache it separately, which means having to fetch it all on every request where anything has changed, in addition to the decoding etc on every request.
Re:What is the space overhead of Base64 encoding? by masklinn on Thursday January 31, 2019 @04:43AM (#19043630)
That can also be an advantage, if the connection has a high throughput but a high latency (e.g. cellular networks, still), you'd much rather fetch everything in a single request. There's a slight inefficiency in the inability to independently cache assets, but even that's not necessarily a big issue: you'd mostly inline small assets.
Re:What is the space overhead of Base64 encoding? by skohan on Thursday January 31, 2019 @07:05AM (#19044163)
It still feels like a hack to work around a problem that should be solved at the protocol level. There's no technical reason that multiple assets couldn't be streamed over a single TCP connection. If it's a common use-case that a number of assets need to be loaded at once to display a web page, then this should be supported by HTTP.
Re:What is the space overhead of Base64 encoding? by jenscow on Thursday January 31, 2019 @07:25AM (#19044241)
Great idea. Let's call it HTTP/2.

https://en.wikipedia.org/wiki/HTTP/2

Re:What is the space overhead of Base64 encoding? by TheCycoONE on Thursday January 31, 2019 @07:00AM (#19044145)
You can bump that scenario down a layer to http2 push and get the best of both worlds.