- From: James M Snell <jasnell@gmail.com>
- Date: Sun, 12 May 2013 19:54:13 -0700
- To: William Chan (陈智昌) <willchan@chromium.org>
- Cc: HTTP Working Group <ietf-http-wg@w3.org>
Definitely interested in helping out on this also. Will have to see what the schedule and plan is in late June, however. On Sun, May 12, 2013 at 2:56 PM, William Chan (陈智昌) <willchan@chromium.org> wrote: > I know we talked about this at the last interim meeting, but as far as I > know, nothing has happened on this front. Has anyone started on this yet? > I'd love to see us make progress on this front. I also think that this will > help clarify corners of the spec, since everytime we raise an ambiguity, we > really oughta write a test for it. > > Here are my rough thoughts here: > * Again, host all code/configuration on github, probably in the http2 > organization again > * Run a http2 test server in EC2. Host client test on it > * Have code for a server test. Uses a test client and a set of test pages. > Servers must host the pages at well defined paths. > * Um, think something up for proxies. Not hard, but I'm running outta time > here. > > Mostly, I want to get people thinking about this and wanted to see who's > interested in working on this. I actually don't want to work on it since as > many people know, I'm technically part-time (20%) employed now > hacking/traveling. But if no one steps up to contribute here, I will > probably do so. That would be terrible because I'm busy traveling most of > the time, and if people left it up to me, I would write everything in Go > just to learn it. I know Mark has some basic SPDY code in Python that would > be a good foundation for this work. > > So yeah, let's get started on this testing thing. I think it's important.
Received on Monday, 13 May 2013 02:55:00 UTC