- From: Jonas Sicking <jonas@sicking.cc>
- Date: Tue, 20 Apr 2010 11:34:42 -0700
- To: Anne van Kesteren <annevk@opera.com>
- Cc: "public-webapps@w3.org" <public-webapps@w3.org>
On Mon, Apr 19, 2010 at 6:47 PM, Anne van Kesteren <annevk@opera.com> wrote: > On Tue, 20 Apr 2010 00:38:54 +0900, Jonas Sicking <jonas@sicking.cc> wrote: >> >> As I've said before. I'd be interested in implementing UMP in firefox >> if we can come up with a reasonable API for using it. I.e. a separate >> constructor or flag or similar on XHR. This is assuming that UMP is a >> reasonable subset of CORS. > > Have you looked at the proposal I put in XHR2? It sets certain flags in CORS > that make it more or less the same as UMP. I don't really see why we would > need UMP if we have that. It looks ok to me, though somewhat lacking on details. What happens if you call x = new XMLHttpRequest("foopy"); or x = new XMLHttpRequest(undefined); You should probably define that the 'anon' argument is a boolean so that the normal conversion rules automatically are applied. I'm also wondering if the UMP guys are happy with this syntax. >> There has been suggestions of changing header names. I'm not a big fan >> of the current names, but if we're going to fix them, i'd rather see a >> coherent strategy for all CORS headers than random spot fixes. > > Does that mean you would be willing to remove support for the current header > names? If not I'm not sure if it is worth it. But if you are I will make a > proposal. Yeah, the goal would definitely be to drop the old header names. We probably couldn't drop them right away, but would need a phase-out period. I think this would still be doable, but the longer we wait the less that is going to be true. Also, it requires everyone to be on board with this change, including webkit and Microsoft. / Jonas
Received on Tuesday, 20 April 2010 18:35:35 UTC