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

Re: CORS versus Uniform Messaging? [Was: [cors] Uniform Messaging, a CSRF resistant profile of CORS]

From: Mark S. Miller <erights@google.com>
Date: Fri, 4 Dec 2009 10:30:02 -0800
Message-ID: <4d2fac900912041030s796b4d25vba991c5373396cbd@mail.gmail.com>
To: Arthur Barstow <art.barstow@nokia.com>
Cc: Tyler Close <tyler.close@gmail.com>, public-webapps <public-webapps@w3.org>
We intend that Uniform Messaging be adopted instead of CORS. We intend
that those APIs that were expected to utilize CORS (SSE, XBL) instead
utilize Uniform Messaging. As for XHR2, we intend to propose a similar
UniformRequest that utilizes Uniform Messaging.

We intend the current proposal, Uniform Messaging Level One, as an
alternative to the pre-flight-less subset of CORS. As for the
remaining Level Two issues gated on pre-flight, perhaps these are best
addressed after we settle the SOP restrictions that server-side app
authors may count on, which therefore protocols such as CORS and
Uniform Messaging must uphold.


On Fri, Dec 4, 2009 at 10:04 AM, Arthur Barstow <art.barstow@nokia.com> wrote:
> Mark, Tyler,
>
> On Nov 23, 2009, at 12:33 PM, ext Tyler Close wrote:
>
>> I made some minor edits and formatting improvements to the document
>> sent out on Friday. The new version is attached. If you read the prior
>> version, there's no need to review the new one. If you're just getting
>> started, use the attached copy.
>
> Would you please clarify your intent with your Uniform Messaging proposal
> vis--vis CORS and your expectation(s) from the Working Group?
>
> -Art Barstow
>
>



-- 
    Cheers,
    --MarkM
Received on Friday, 4 December 2009 18:30:52 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:35 GMT