W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2009

Re: [cors] TAG request concerning CORS & Next Step(s)

From: Henry S. Thompson <ht@inf.ed.ac.uk>
Date: Thu, 22 Oct 2009 19:00:02 +0100
To: "Anne van Kesteren" <annevk@opera.com>
Cc: "Jonas Sicking" <jonas@sicking.cc>, "Arthur Barstow" <Art.Barstow@nokia.com>, public-webapps <public-webapps@w3.org>
Message-ID: <f5b63a7wbq5.fsf@hildegard.inf.ed.ac.uk>
Hash: SHA1

Anne van Kesteren writes:

> On Wed, 24 Jun 2009 19:22:35 +0200, Henry S. Thompson
> <ht@inf.ed.ac.uk>  wrote:
>> One point of clarification: my (admittedly imperfect) understanding
>> was that the most important parts of CORS have to be implemented
>> _server_-side for the proposal to achieve its goals.  If that's true,
>> browser deployment alone is insufficient.  Is that a misunderstanding
>> on my part?
> As was pointed out elsewhere in this thread it was.
> I was wondering if the TAG considers this item closed or wishes to
> know  something more, in which case I'd like to hear about it! I'm
> trying to  wrap up email threads and this is one of them. Thanks!

Sorry for the delay -- the discussion has clarified the current
relevance of client-side implementations, and as far as that goes the
TAG is happy.

We do assume that demonstrating interoperable server-side
implementation will be a necessary part of your CR exit criteria --
could you please confirm that?


- -- 
       Henry S. Thompson, School of Informatics, University of Edinburgh
                         Half-time member of W3C Team
      10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
                Fax: (44) 131 651-1426, e-mail: ht@inf.ed.ac.uk
                       URL: http://www.ltg.ed.ac.uk/~ht/
[mail really from me _always_ has this .sig -- mail without it is forged spam]
Version: GnuPG v1.2.6 (GNU/Linux)

Received on Thursday, 22 October 2009 18:00:49 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:20 UTC