On 06/05/2014 11:53 AM, Nick White wrote:
As was mentioned, external resources like variously sized images would probably be the trickiest thing to figure out good ways around. IIRC SPDY has some inlining multiple resources in the same packet sort of stuff, which we might be able to take advantage of to help here (it's been ages since I read about it, though).
When using SPDY browsers multiplex and interleave all requests over a single TCP connection, while with HTTP they typically open around six parallel connections for HTTPS. HTTP pipelining also tends to be disabled in desktop browsers, which makes it relatively easy to figure out the size of individual requests & thus potentially the page viewed or edited.
With Apple finally adding SPDY support in the latest Safari release (after IE ;) support should soon grow beyond the 67% of global equests claimed currently [1], which is good for performance, security and architectural simplicity.
Ops has a draft goal of experimental SPDY support in Q2, so it seems that it's going to happen soon. Also see bug 33890 [2].
Gabriel
[1]: http://caniuse.com/spdy [2]: https://bugzilla.wikimedia.org/show_bug.cgi?id=33890