RE: Resource Timing

The case I'm mostly worried about is where we (facebook.com) host our static resources on a different domain (fbcdn.net). I'd like some way to allow fbcdn.net to "opt in" to giving timing information to facebook.com. At one point CORS (http://www.w3.org/TR/cors/) was mentioned as a possible solution.

I look forward to seeing what you come up with Zhiheng. Thanks!

              --jason


-----Original Message-----
From: Bryan McQuade [mailto:bmcquade@google.com] 
Sent: Tuesday, August 24, 2010 12:32 PM
To: Zhiheng Wang
Cc: Jason Sobel; public-web-perf@w3.org
Subject: Re: Resource Timing

Interesting. Can you expand on the meta header approach?

I assume you are referring to a case where a child iframe is on a
different origin. In that case it would not be appropriate to leak the
timing info for the frame up to the parent. But it sounds like this
meta header might allow the child frame to give permission to leak the
info to the parent?

On Tue, Aug 24, 2010 at 12:49 PM, Zhiheng Wang <zhihengw@google.com> wrote:
>     The immediate questions for ResourceTiming is how to maintain privacy
> while exposing those timing information.
> So far using meta header on top of the same origin policy seems to be the
> way to start. An update should be available
> later this week.
> cheers,
> Zhiheng
>
>
> On Mon, Aug 23, 2010 at 12:41 PM, Jason Sobel <jsobel@facebook.com> wrote:
>>
>> Hey all-
>>
>> Looks like you're making great progress on navigation timing -- very
>> exciting!
>>
>>
>>
>> Do you have any thoughts on polishing and implementing resource timing?
>> That data is very interesting to us at Facebook so I'm hoping it will be
>> available in all the major browsers sooner rather than later.
>>
>>
>>
>> Thanks much!
>>
>>
>>
>>               --jason
>>
>>
>

Received on Tuesday, 24 August 2010 19:37:55 UTC