- From: 陈智昌 <willchan@chromium.org>
- Date: Sun, 12 May 2013 18:56:32 -0300
- To: HTTP Working Group <ietf-http-wg@w3.org>
- Message-ID: <CAA4WUYh6RQHPiKAdyURA5-L8j5Bdg=DefV_TxehCM2-ZMQgxFw@mail.gmail.com>
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 Sunday, 12 May 2013 21:57:00 UTC