- From: Jatinder Mann <jmann@microsoft.com>
- Date: Wed, 6 Jun 2012 21:34:17 +0000
- To: James Simonsen <simonjam@chromium.org>
- CC: "public-web-perf@w3.org" <public-web-perf@w3.org>
> Personally, I'd rather rely on someone else's definition than crafting our own. > But if CORS isn't stable enough, then I guess we'll have to roll our own. As we discussed in the call today, the CORS Section 7.2 Resource sharing check processing model has some steps that don't make sense in Resource Timing. E.g., the concept of 'omit credentials flag' in steps 4 and 5 don't make sense. As the processing model here is only a few sentences, I think a tailored processing model for Resource Timing might make more sense. I'll send out my proposed text update. > I haven't thought about Web Workers at all. Presumably, we'll come across similar > issues with User Timing. Maybe we should just try to ship what we've got and punt > workers out to v2? > > I do agree with your points though. I think those make the most sense. I'm inclined to agree as well. I think the design of shared workers will require additional thought which we can tackle in V2.
Received on Wednesday, 6 June 2012 21:35:52 UTC