| |||||||||||||
|
| |||||||||||||
Reducing HTTP latency with SPDYReducing HTTP latency with SPDYPosted Nov 19, 2009 0:39 UTC (Thu) by samroberts (subscriber, #46749)In reply to: Reducing HTTP latency with SPDY by dps Parent article: Reducing HTTP latency with SPDY
> Last time I looked at BEEP it was incredibly verbose
Beep framing overhead looks like this. You call this incredibly verbose? Compared to HTTP?
MSG 0 1 . 52 120
XML shows up only briefly during channel setup, and is quite minimal:
I: MSG 0 1 . 52 115
Transporting HTTP over BEEP would allow multiple, simultaneous, bi-directional HTTP requests in parallel, multiplexing use of the same TCP connection.
I don't think it will happen, but I don't think SPDY will either :-)
(Log in to post comments)
Reducing HTTP latency with SPDY Posted Nov 19, 2009 12:32 UTC (Thu) by jzbiciak (✭ supporter ✭, #5246) [Link] I can see one way SPDY happens: Google supports it on all their servers, and pushes support for it into Chrome/Chromium and, crucially, their mobile browser in Android. Throw on top of that a Google-operated caching proxy service that Android users can use (as transparently as possible, of course!) so that browsing the Internet from your mobile suddenly got 2x - 3x faster without having to upgrade to 4G or what-have-you, and I think you'll see a lot of pressure for others to support SPDY. Meanwhile, Google laughs all the way to the bank monetizing the extensive marketing data they've collected from these proxies about what people are actually browsing on their Android phones. Or, am I just extra cynical in the morning?
Reducing HTTP latency with SPDY Posted Nov 19, 2009 12:54 UTC (Thu) by michel (subscriber, #10186) [Link]
I would not describe that as cynical, but rather as an interesting strategy well in line with Google's business model
Reducing HTTP latency with SPDY Posted Nov 27, 2009 0:12 UTC (Fri) by deleteme (guest, #49633) [Link]
I assure you that those logs are available from many big phone companies.
|
|
||||||||||||