<trackbot> Date: 22 August 2012

<plh> zaki, this is per

Resource Timing

Jatinder: We need to close on whether setResourceTimingBufferSize method should truncate the buffer or not. I'll follow up on the mailing list.

Navigation Timing 2

Arvind: Based on feedback, I have added an attribute for radioAwakeStart and radioAwakeEnd. These will be optional attributes. On mobile devices, the time spent waiting for the radio to be turned on during a navigation can be significant. I will submit the changes and Jatinder please also review.

HARS Spec

Arvind: I have a draft prepared for the HARS spec and will be checking in the draft into the w3c respository soon.

Plh: We should update the charter to include the HARS specification with our next charter update.
... I'm going to take an action to put together a draft for the new charter.

Arvind: Jatinder, can you send out an email with the problem statement and potential solutions for the background activity this week? We can look at this idea and decide whether or not we want to include this in the next charter.

Charter

plh: Is Tony still interested in the memory leak API?

Arvind: He is out this week, but we should get him to also send out a problem statement and potential solutions for the memory leak API and the working group can analyze whether they want to take this or not in the next charter.

plh: Alois, what about the bandwidth API?

Arvind: Actually, I believe we discussed that this one should be better tracked in other network WGs, rather than this Web Perf.

plh: I will remove this from our list.
... The other ones is media resource timing. This came up in the discussion with NetFlix.

Arvind: Jatinder, do you recall?

Jatinder: There were two parts, one was whether we should provide additional data for video, audio and flash, like byte ranges or only a single entry. I believe this we are interested in doing in Resource Timing 2.
... The other point that Mark brought up was to use the Timing specs to make real time decisions, and we decided that was out of scope for this WG.

plh: Jatinder can you send out a sentence describing what this should look like in the charter?

Jatinder: Will do.

Alois: There was another issue that we wanted to have covered. That was with some sites using a busy loop on the unload to attempt to send up data. This sounds like a good opportunity for the charter.

Jatinder: Yes, I recall Jason Weber brought up this issue at TPAC. Let me respond with a problem statement and potential solutions to the mailing list for the charter.

plh: Sounds good.
... We also need to discuss testing of the specifications, however, I think that can wait for a bit.

Alois: There was one more issue that we needed to close. For Velocity Europe, we needed to choose a representative that would talk about the Web Performance WG.
... Since I will be at the conference I can present.

Plh: Sounds good.

This is scribe.perl Revision: 1.136  of Date: 2011/05/12 12:01:43  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

No ScribeNick specified.  Guessing ScribeNick: JatinderMann
Inferring Scribes: JatinderMann
Default Present: [Microsoft], +1.408.203.aaaa, Plh, +43.732.908.2aabb
Present: [Microsoft] +1.408.203.aaaa Plh +43.732.908.2aabb Alois plh arvind jatinder

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 22 Aug 2012
Guessing minutes URL: http://www.w3.org/2012/08/22-webperf-minutes.html
People with action items: