On Sun, Oct 27, 2013 at 6:22 AM, Jonathan Bond-Caron
jbo...@gdesolutions.com wrote:
You wouldn't get faster delivery with a P2P-like algorithm?
e.g.:
Server sends a header:
Cache-clients: my-neighbor.com:4000, my-other-neighor.com:6000
Some security considerations for sure but your claim
+ 1 to François's comments.
You're not saying that gzipping and wise pre-fetching and parallel download
of scripts don't improve page load times. Or are you?
- We already have transfer-encoding in HTTP, and yes, you should definitely
use it!
- Prefetching is also an important optimization, but
exactly what AppCache did, create a manifest which lists all the resources,
and let HTTP do the rest: each file can be downloaded and updated
individually, etc.
ig
[1]
http://www.chromium.org/developers/design-documents/software-updates-courgette
On Thu, Oct 24, 2013 at 11:17 PM, Ilya Grigorik
On Fri, Oct 25, 2013 at 6:24 AM, Jonathan Bond-Caron
jbo...@gdesolutions.com wrote:
On Wed Oct 23 10:17 PM, Ilya Grigorik wrote:
In short, pitching zip bundling as a performance optimization is a
complete misnomer. If anything, it will only make things worse, even
for HTTP 1.x clients
Hey all. Late to the discussion here, but after scanning the thread,
figured it might be worth sharing a few observations...
The fact that we have to bundle files at the application layer is an
unfortunate limitation of HTTP 1.x protocol. Specifically, because HTTP 1.x
forces us to serializes
5 matches
Mail list logo
