16:55:43 RRSAgent has joined #webperf 16:55:43 logging to http://www.w3.org/2012/09/19-webperf-irc 16:55:45 RRSAgent, make logs world 16:55:45 Zakim has joined #webperf 16:55:47 Zakim, this will be WPWG 16:55:47 I do not see a conference matching that name scheduled within the next hour, trackbot 16:55:48 Meeting: Web Performance Working Group Teleconference 16:55:48 Date: 19 September 2012 17:00:46 Alois has joined #webperf 17:01:06 present+ JatinderMann 17:01:09 present+ Alois 17:01:13 present+ Tobie 17:02:13 present+ Arvind 17:02:38 plh has joined #webperf 17:02:44 trackbot-ng, start telcon 17:02:47 RRSAgent, make logs world 17:02:49 Zakim, this will be WPWG 17:02:50 Meeting: Web Performance Working Group Teleconference 17:02:50 Date: 19 September 2012 17:02:53 I do not see a conference matching that name scheduled within the next hour, trackbot 17:02:58 zakim, this is per 17:03:04 ok, plh; that matches RWC_web-per()1:00PM 17:03:20 zakim, passcode? 17:03:24 the conference code is 97373 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), plh 17:03:44 +Philippe 17:04:01 present+ Plh 17:04:05 zakim, aaaa is Arvind 17:04:05 +Arvind; got it 17:04:12 zakim, aabb is Alois 17:04:14 +Alois; got it 17:04:24 +gmandyam 17:04:49 present+ Gary 17:04:59 Mandyam, Giridhar 17:05:58 gmandyam has joined #webperf 17:06:27 Giri Mandyam from Qualcomm Innovation Center joining the call 17:06:38 zakim, gmandyam is Giri_Mandyam 17:06:38 +Giri_Mandyam; got it 17:07:07 + +44.791.941.aacc 17:08:29 Klas, Guenter 17:08:42 +komoroske 17:09:17 present+ Mandyam, Giridhar 17:09:28 present+ Klas, Guenter 17:09:34 present+ Tony 17:09:40 zakim, komoroske is really Tony 17:09:40 +Tony; got it 17:09:59 tonyg has joined #webperf 17:10:04 zakim, aacc is Gunter 17:10:04 +Gunter; got it 17:10:48 zakim, passcode? 17:10:48 the conference code is 97373 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), plh 17:11:37 Topic: Mobile Networking 17:13:01 Philippe: We have invited Giri Mandyam for Qualcomm Inovation Center, Gunter Klas from VodoPhone and others from ATT to discuss mobile networking performance improvements to include in our next charter. 17:16:55 Gunter: There are many differences between phone operating systems. On application level, to send short messages a lot of over head is required to send signals. Just to send a few bytes to the application server, that can trigger signals between the mobile network and application. This can cause a burden on the network, potentially leading to network outages. The user is also impacted by the increased signaling from the mobile home, as this impacts the 17:19:23 ...There have been discussions in many groups about this problem. There are examples of solutions today where the client captures signals on the client side. In terms of trying to solve the problem when the problem has arisen. We have documentation like the Application Developer Guide. But we wanted to work with the standards group. 17:21:45 ... Which programming paradigms have what consequences on the mobile networking. We have documentation that covers those specific behaviors in iPhone, Andriod and Windows phones. I feel that there is a gap between HTML5 applications that are running on a phone where the mobile network is impacted. 17:24:10 Giri: With new web technologies, like web sockets, there needs to be battery life concerns. Web sockets are a great replacement to XHRs for keeping a presistant connection to the server. When developers start sending dummy bytes on the sockets, we lose the benefits of power saving modules on the phones. What are the kind of the signaling changes that need to be taken place. Seems like mobile issues are not being concerned to the degree that they should 17:25:46 Gunter: We don't currently have a lot of data on the new web technologies. 17:26:24 Giri: Thats also because these are new technologies and we don't yet have the adoption. But that doesn't mean the Web Perf WG shouldn't be forward looking. 17:27:36 Gunter: It would be good to understand if guidelines for native mobile applications should use the same paradigm as web applications. 17:30:10 plh: We haven't done best practices documentation in this working group, but we have been working on APIs to help improve performance, like battery life, using requestAnimationFrame, Page Visibility, etc. 17:31:16 Giri: In the WebRTC, they are looking at a stats interface where they will provide feedback on rtc, rtp interfaces that will provide data up through JavaScript. Is this something that that working group should use, or is this something the Web Perf WG should look at? 17:32:56 Jatinder - WebRTC stats I/F looks at RTCP/RTP performance metrics. Thanks - Giri 17:43:39 Jatinder: We are very interested in mobile performance improvements. Please do send your specific requests to the mailing list so we can discuss. 17:54:44 -Arvind 17:54:45 -Giri_Mandyam 17:54:45 -[Microsoft] 17:54:46 -Tony 17:54:46 -Gunter 17:54:46 -Philippe 17:54:47 -Alois 17:54:49 RWC_web-per()1:00PM has ended 17:54:51 Attendees were [Microsoft], +1.650.253.aaaa, +43.664.853.aabb, Philippe, Arvind, Alois, Giri_Mandyam, +44.791.941.aacc, Tony, Gunter 17:55:04 Plh: Let's discuss test case status next week. 17:55:32 Jatinder: Arvind, let's get the information for the F2F and Workshop, so we can send out an email. 17:55:47 Plh: I am drafting text. Let's follow up and get that out. 17:55:55 rrsagent, generate minutes 17:55:55 I have made the request to generate http://www.w3.org/2012/09/19-webperf-minutes.html JatinderMann 18:58:55 zaki, bye 18:58:59 zakim, bye 18:58:59 Zakim has left #webperf 18:59:02 rrsagent, bye 18:59:02 I see no action items