Firefox/Projects/Resource Packages: Difference between revisions

Updating to new project template
(Adding resource package link)
 
(Updating to new project template)
 
Line 1: Line 1:
== Participants ==
__NOTOC__
The goal for this project is to implement a standard approach to transmit file resources in a single package for use in a web page, including (but not exclusively) JS, CSS, images. It should be a standard that all browsers makers can easily implement, and that is backwards compatible with browsers that do not support it. We also want a solution that works for all types of resources, and one that doesn’t require any new tools, file types or protocols.


limi, vlad
* Champion: limi
* Project Lead: vlad?
* Project Members: jlebar
* QA: TBD


== Current state ==
== Status ==
* <onlyinclude>ON RUNWAY</onlyinclude>
** Proposal has been finalized, ready for implementation
* Tracking bug: {{bug|529208}}
* Proposal: http://limi.net/articles/resource-packages


Proposal, rev 2:
== Goals ==
http://limi.net/articles/resource-packages
*  Make it possible to serve all the resources (images, stylesheets, javascript) required by a page in a single HTTP request, freeing up the other parallel requests to fetch resources that are page-specific.
* Be as simple to implement as possible, so anyone with a passing familiarity with HTML should be able to perform the optimization.
* Be entirely transparent to browsers that do not support it.
* Avoid retransmission of existing resources.
* Use existing tools that are widely used on all platforms.
* Support the “80% use case” over adding a lot of complexity to the spec.


== Next steps ==
== Non-Goals ==
*  Invent new file formats
* Invent new compression formats


Update spec to use the offline manifest format with Vlad.
== Timeline / Milestones ==
 
== Requirements ==
* Benchmark results as early as possible, with real-world web sites and realistic latency.
 
== Dependencies ==
 
== Testing ==
 
== Related Projects ==
canmove, Confirmed users
570

edits