- From: Wayne Carr <wayne.carr@linux.intel.com>
- Date: Fri, 12 Apr 2013 12:20:58 -0700
- To: public-closingthegap@w3.org
On 3/28/2013 6:28 AM, Dominique Hazael-Massieux wrote: > [snip] > > Network optimizations > --------------------- > Downloading or uploading large assets for a given Web app requires the > Web app to be running, and can't easily take advantage of optimal > network situations (e.g. using Wifi rather than 2G); offering an API > that would enable this would make Web apps more capable, potentially > less detrimental to the network, and more performant. > > The Web Performance Working Group proposed new charter includes work on > a beacon API, and on network resource priorities, both of which would > help in this field. > http://www.w3.org/2013/01/webperf.html Wouldn't Beacon in the proposed Performance WG charter be only for upload? Proposed charter says "An interoperable API for site developers to asynchronously transfer data from the user agent to a web server, with a guarantee from the user agent that the data will be eventually sent." Couldn't the upload part be covered by the new WebApps offline storage topic elsewhere in your summary? > > Possible W3C actions: > * short term: start a Community Group to draft a spec? (or bring it to > the existing Network-Friendly App and WebApp Best Practices CG?) > * increase resources in WebPerf Working Group to help speed up the work > > Rather than a CG, could this be covered by providing use cases for Beacon and maybe resource priorities in the Performance WG and the new offline work in the Web Apps WG? [snip]
Received on Friday, 12 April 2013 19:21:51 UTC