18:00:57 RRSAgent has joined #webperf 18:00:57 logging to http://www.w3.org/2013/02/27-webperf-irc 18:00:59 RRSAgent, make logs world 18:00:59 Zakim has joined #webperf 18:01:01 Zakim, this will be WPWG 18:01:01 I do not see a conference matching that name scheduled within the next hour, trackbot 18:01:02 Meeting: Web Performance Working Group Teleconference 18:01:02 Date: 27 February 2013 18:02:08 plh has joined #webperf 18:02:16 Alois has joined #webperf 18:02:18 zakim, this is per 18:02:18 ok, plh; that matches RWC_web-per()1:00PM 18:02:28 +Plh 18:02:32 + +1.650.701.aaaa 18:02:36 +[Microsoft] 18:02:45 + +43.732.908.2aabb 18:02:57 present+ DanielAustin, plh, Alois, JatinderMann, Arvind 18:05:03 Topic: Test Cases 18:05:41 http://w3c-test.org/webperf/tests/submission/Intel/resource-timing/ 18:06:07 Jatinder: I noticed that Resource Timing test cases still don't work in IE. I'll follow up in mail. 18:06:11 Topic: Beacon API 18:06:30 https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/Beacon/Overview.html 18:06:44 + +1.650.214.aacc 18:06:53 simonjam has joined #webperf 18:07:02 https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/Beacon/Overview.html 18:08:19 beacon("POST", "/log", analyticsData); 18:18:37 James: I want to make sure that the spec is very clear that just because you are building data on the unload, we don't want to make people think that we're going to wait minutes to make this call. 18:19:30 James: What if we have 5GBs of data? Do we want to set limits? 18:22:03 I added a link to the draft from http://www.w3.org/wiki/Web_Performance/Publications 18:22:23 Jatinder: Sounds reasonable that we put in some limits. Don't want the browser to wait forever. 18:23:39 Arvind: Should we keep the domain cookie or not for this response? I'm not sure what we should do here. 18:23:54 James: What about XHRs? 18:24:11 Daniel: If the beacon is ad related I don't expect it to impact cookies. 18:24:32 Arvind: We should make sure that the spec text doesn't say gauranteed, it should say best effort. 18:26:24 -[Microsoft] 18:26:25 - +1.650.701.aaaa 18:26:26 -Daniel_Austin 18:26:27 -Plh 18:26:27 - +1.650.214.aacc 18:26:27 - +43.732.908.2aabb 18:26:28 RWC_web-per()1:00PM has ended 18:26:28 Attendees were Daniel_Austin, Plh, +1.650.701.aaaa, [Microsoft], +43.732.908.2aabb, +1.650.214.aacc 18:27:24 Jatinder: There were some considerations that I hadn't included in this spec. What if the browser is shutdown? Should we persist this information on disk and attempt to send it out next time? What if the browser gets an error in the response, does it attempt to send the data out again? 18:28:06 James: I think we should stick with the current, simple model where we attempt to send it once asynchrnously. If there is demand to increase our attempts or do some persisting work, we can consider that in L2 or based on feedback. 18:28:46 Jatinder: Okay, I'll keep the approach simple and move away from gauranteeing this will work to trying a best effort attempt. 18:29:28 Arvind: I want to make sure that Firefox reviews this spec as well, as they had privacy concerns with the Ping API. I can see that this API is different from Ping and tries to accomplish something different, but we should make sure there are no privacy concerns. 18:29:53 Jatinder: I'll update the spec based on today's feedback and send mail to the mailing list for additional feedback. I'll make sure Boris is CC'd. 18:30:04 Topic: Next Week's Agenda 18:30:13 Jatinder: Should we cover prerender or diagnostics next week? 18:30:25 Arvind: Let's cover prerender two weeks from now, as I will be out next week. 18:30:38 Alois: We can cover diagnostics next week. I'll follow up with you offline. 18:30:48 rrsagent, generate minutes 18:30:48 I have made the request to generate http://www.w3.org/2013/02/27-webperf-minutes.html JatinderMann 20:06:36 Zakim has left #webperf 20:41:38 plh2 has joined #webperf 20:49:50 plh2 has left #webperf