- From: Tobie Langel <tobie@w3.org>
- Date: Tue, 24 Sep 2013 10:09:37 +0200
- To: Wang, Jing J <jing.j.wang@intel.com>
- Cc: James Graham <james@hoppipolla.co.uk>, "public-test-infra@w3.org" <public-test-infra@w3.org>
On Tuesday, September 24, 2013 at 2:19 AM, Wang, Jing J wrote: > > > I don't know exactly what you mean. However, let me try to explain. > > > > > > The server reserves the "pipe" query parameter for its own use. The value of this parameter specifies, in effect, a server internal function that the response will be passed through. In this case I am suggesting that the "config" function be defined as something like: > > > > > > def config(request, response): > > > response.content = response.content % config_dict > > > > > > This means that the replacement will be transparent to the browser; it will just see static files with the correct values for each parameter in. > > Thanks James for explanation. So, server helps do the transparent replacement, but my concern is it make TC very dependent on specific Web server. I think that's an acceptable tradeoff to make for a given subset of tests, granted: 1) the server is available under W3C's software license, 2) it's sufficiently portable, and 3) the transformation is simple enough that it would be easy to implement as middleware on top of a different server. --tobie
Received on Tuesday, 24 September 2013 08:09:17 UTC