social
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Social] Fwd: GNU/social legacy


From: hellekin
Subject: Re: [Social] Fwd: GNU/social legacy
Date: Wed, 12 Dec 2012 21:29:51 -0300
User-agent: Mozilla/5.0 (X11; Linux i686; rv:10.0.10) Gecko/20121028 Icedove/10.0.10

On 12/12/2012 05:58 PM, Rob Myers wrote:
>>
>>     It is an inefficient protocol that is about to be replaced by SPDY.
>>
>> Really? :)
> 
> http://www.infoq.com/news/2012/11/http20-first-draft
> 
*** According to the Wikipedia article on SPDY:

SPDY does not replace HTTP; it modifies the way HTTP requests and
responses are sent over the wire. This means that all existing
server-side applications can be used without modification if a
SPDY-compatible translation layer is put in place. When sent over SPDY,
HTTP requests are processed, tokenized, simplified and compressed. For
example, each SPDY endpoint keeps track of which headers have been sent
in the past requests and can avoid resending the headers that have not
changed; those that must be sent are sent compressed.
The IETF working group for HTTPbis is planning to start working on HTTP
2.0, and will put out a call for proposals. SPDY
(draft-mbelshe-httpbis-spdy-00) will be used as a starting point.

http://en.wikipedia.org/wiki/SPDY

It's clear that a single connection sounds much better than 4, or as
we're seeing more and more with "HTTP accelerators", 16.

I didn't look at the specification, but that specific point sounds much
better than HTTP already.

==
hk

Attachment: signature.asc
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]