- From: <piranna@gmail.com>
- Date: Fri, 4 Oct 2013 07:09:47 +0200
- To: Mhyst <mhysterio@gmail.com>
- Cc: public-restrictedmedia@w3.org
- Message-ID: <CAKfGGh1aP+gOM-762MD0-K+GpZs8XAYcxp6D6ZO_sDcP80JRCg@mail.gmail.com>
Let's hope you don't find them... Honestly, I'm really pesimist after this news has surfaced :-( El 04/10/2013 01:25, "Mhyst" <mhysterio@gmail.com> escribió: > I'd need to read the whole rfc, but from what I see, HTTP/2.0 must provide > backwards compatibilty, so ... > > GET / HTTP/1.1 > > Would force the server to behave like a HTTP/1.1 server. > > Anyway, the new version tries to make web surfing faster. I may not like > headers compression or the server sending me content I didn't request... > but while I can keep geting a web file by telnet, I won't complain. That is > until I read the specification and find something wrong. > > > > El 4 de octubre de 2013 00:42, piranna@gmail.com <piranna@gmail.com>escribió: > >> > Well, HTTP isn't affected by EME at all. HTTP protocol can be used to >> > transport any kind of information. >> > >> The next logic step. I would take a look on HTTP 2.0 specifications, >> maybe we could find some surprises... >> >> >> -- >> "Si quieres viajar alrededor del mundo y ser invitado a hablar en un >> monton de sitios diferentes, simplemente escribe un sistema operativo >> Unix." >> – Linus Tordvals, creador del sistema operativo Linux >> > >
Received on Friday, 4 October 2013 05:10:15 UTC