- From: Alex Russell <slightlyoff@chromium.org>
- Date: Mon, 12 Oct 2009 20:29:32 -0700
On Mon, Oct 12, 2009 at 3:38 PM, Aryeh Gregor <Simetrical+w3c at gmail.com> wrote: > On Mon, Oct 12, 2009 at 5:14 PM, Maciej Stachowiak <mjs at apple.com> wrote: >> And the standard would have to describe what it actually does, which would >> probably require some input from Microsoft. At some point, to advance on the >> IETF standards track, it would need multiple interoperable implementations. >> That prospect does not seem likely. > > You could define a generic syntax that allows any browser to use XUAC, > and count IE and Chrome Frame as independent interoperable > implementations. ?Of course, they'd respond to the header in slightly > different ways (keying off different strings), but only as required by > the spec. That's what I was considering. Only token parsing for the values really needs to be defined. Behavior in response does not.
Received on Monday, 12 October 2009 20:29:32 UTC