- From: Kingsley Idehen <kidehen@openlinksw.com>
- Date: Mon, 15 Jul 2013 12:40:48 -0400
- To: www-tag@w3.org
- Message-ID: <51E42610.6020803@openlinksw.com>
On 7/15/13 12:22 PM, Appelquist Daniel (UK) wrote: > Hy Yves - FYI I created an issue in github to track feedback on the http > spec and I took the liberty of assigning it to you. I'm not sure if we > have any meaningful feedback to share, but if we do I'm pretty sure you > are the right person to coordinate. :) > > > https://github.com/w3ctag/spec-reviews/issues/4 > > Thanks, > Dan seeAlso: 1. http://linkeddata.uriburner.com/about/id/entity/https/github.com/w3ctag/spec-reviews/issues -- Linked Data URI that denotes (names) TAG issues collection 2. http://linkeddata.uriburner.com/describe/?url=http%3A%2F%2Flinkeddata.uriburner.com%2Fabout%2Fid%2Fentity%2Fhttps%2Fgithub.com%2Fw3ctag%2Fspec-reviews%2Fissues -- alternative view oriented towards faceted exploration of relations 3. http://bit.ly/XCZrf4 -- Overview by Issue Creator via W3C issues tracking system. Kingsley > > > On 10/07/2013 08:38, "Appelquist Daniel (UK)" > <Daniel.Appelquist@telefonica.com> wrote: > >> On 10/07/2013 04:07, "Noah Mendelsohn" <nrm@arcanedomain.com> wrote: >> >>> A new draft of HTTP 2.0 is available at [1]. Since this is a significant >>> change to one of the three "pillars" or Web architecture, it seems to me >>> that the TAG should at least study this in detail. >>> >>> Noah >>> >>> [1] http://tools.ietf.org/html/draft-ietf-httpbis-http2-04 >>> >> Thanks for posting this, Noah! I also note some raucous discussion on this >> going on here: >> >> http://tech.slashdot.org/story/13/07/09/1455200/http-20-will-be-a-binary-p >> r >> otocol >> >> And an interesting post here by Poul-Hennings Kamp (@bsdphk): >> >> https://www.varnish-cache.org/docs/trunk/phk/http20.html >> >> @Yves - as you've been closest to this work do you think you could post >> your thoughts? What are the key differences between HTTP 1.1 and HTTP 2.0 >> that we ought to be focusing on from a Web Architecture perspective. I >> will note that the TAG held a session on SPDY in 2011 with Mike Belshe: >> >> http://www.w3.org/2001/tag/2011/11/04-minutes.html#item01 >> >> It's somewhat instructive reading those minutes, particularly about how >> wide-spready deployment of SPDY might change the way Web Applications are >> architected deployed. To what extent has the SPDY work made it into HTTP >> 2.0? >> >> Is there meaningful review we could do of the HTTP 2.0 work in the context >> of AWWW 2.0, capability URLs, or the JavaScript-related work? What >> assumptions about the use of HTTP are we making in any of this work that >> could potentially be impacted by HTTP 2.0? >> >> Dan >> -- Regards, Kingsley Idehen Founder & CEO OpenLink Software Company Web: http://www.openlinksw.com Personal Weblog: http://www.openlinksw.com/blog/~kidehen Twitter/Identi.ca handle: @kidehen Google+ Profile: https://plus.google.com/112399767740508618350/about LinkedIn Profile: http://www.linkedin.com/in/kidehen
Attachments
- application/pkcs7-signature attachment: S/MIME Cryptographic Signature
Received on Monday, 15 July 2013 16:41:11 UTC