Re: [Navigation Timing] [Resource Timing] Why do some phases not have an explicit end time attribute?

Thanks, can totally understand the requestEnd scenario.

Can anyone shed light on the others?


On 20 December 2012 20:13, James Simonsen <simonjam@chromium.org> wrote:

> The only one I remember the history for is requestEnd. We don't have a
> requestEnd attribute, because we can't make any meaningful distinction
> between requestEnd and responseStart. There's no way of knowing when the
> request bytes actually leave the network card or when the server started
> sending the response.
>
> I think the basic phases were already decided before I joined.
>
> James
>
>
> On Tue, Dec 18, 2012 at 2:19 PM, Andy Davies <dajdavies@gmail.com> wrote:
>
>> OK,
>>
>> I need a history lesson - I've ad a hunt through the archives but can't
>> fnid the answer...
>>
>> Why do some phases of the processing model have explicit end times e.g.
>> redirectEnd, and others have inferred end times e.g. AppCache, TCP, SSL
>> etc.?
>>
>> Can anyone shed some light on it for me?
>>
>> Thanks
>>
>> Andy
>>
>
>