Zip - Revision history

Annevk: /* URLs */

2013-09-19T14:58:38Z

URLs

← Older revision		Revision as of 14:58, 19 September 2013
Line 18:		Line 18:
	\| 1) URLs become a stack. 2) Zip URL needs its own URL object. 3) URL parser needs changing.		\| 1) URLs become a stack. 2) Zip URL needs its own URL object. 3) URL parser needs changing.
	\|-		\|-
	! rowspan="2" \| ~~zip~~-path		! rowspan="2" \| sub-path
	\| rowspan="2" \| A URL gains ~~a zip~~-~~path~~ which is excluded from the request URL, origin computed per usual		\| rowspan="2" \| A URL gains sub-paths which are excluded from the request URL; origin computed per usual
	\| http://example.org/test%!image.jpg ("%!" as separator)		\| http://example.org/test%!image.jpg ("%!" as separator)
	\| /test%!inner.zip%!image.jpg		\| /test%!inner.zip%!image.jpg
Line 26:		Line 26:
	\| generally does not work today		\| generally does not work today
	\|-		\|-
	\| http://example.org/test~~.zip!~~image.jpg ("~~.zip!~~" as separator~~, but request path includes trailing ".zip"~~)		\| http://example.org/test$sub=image.jpg ("$sub=" as separator)
	\| /test.zip!inner.zip!image.jpg		\| /test.zip$sub=inner.zip$sub=image.jpg
	\| possibility for compatibility-shims		\| possibility for compatibility-shims
	\|-		\|-
Line 39:		Line 39:
	\|}		\|}

	While ~~zip~~-path could support relative addressing outside of a zip, it's not clear whether this is desirable.		While sub-path could support relative addressing outside of a zip, it's not clear whether this is desirable.

	~~Need to pick something more unique as separator~~ for data URLs ~~with the zip-path solution. Maybe "$zip=" as Simon suggested~~.		Note that sub-path will also work for data URLs.

	== Fetch ==		== Fetch ==

Annevk: /* URLs */

2013-09-14T09:30:03Z

URLs

← Older revision		Revision as of 09:30, 14 September 2013
Line 40:		Line 40:

	While zip-path could support relative addressing outside of a zip, it's not clear whether this is desirable.		While zip-path could support relative addressing outside of a zip, it's not clear whether this is desirable.

			Need to pick something more unique as separator for data URLs with the zip-path solution. Maybe "$zip=" as Simon suggested.

	== Fetch ==		== Fetch ==

Annevk: caching is hard

2013-09-13T17:47:04Z

caching is hard

← Older revision		Revision as of 17:47, 13 September 2013
Line 40:		Line 40:

	While zip-path could support relative addressing outside of a zip, it's not clear whether this is desirable.		While zip-path could support relative addressing outside of a zip, it's not clear whether this is desirable.

			== Fetch ==

			We need to have a strategy around caching.

			* Just rely on HTTP (might evict early leading to lots of lost bandwidth)
			* Pin fetched URL (if zip) on a per document basis (done for images today, but not implemented at a level that makes generalizing this easy)
			* Pin resource as long as there are references to its data

	== Format ==		== Format ==

Annevk: /* URLs */

2013-09-13T14:08:06Z

URLs

← Older revision		Revision as of 14:08, 13 September 2013
Line 9:		Line 9:
	! relative URLs pointing outside zip		! relative URLs pointing outside zip
	! complexity		! complexity
			! notes
	\|-		\|-
	! sub-scheme		! sub-scheme
Line 23:		Line 24:
	\| rowspan="2" \| √ (../otherimage.jpg)		\| rowspan="2" \| √ (../otherimage.jpg)
	\| rowspan="2" \| 1) URL parser needs changing.		\| rowspan="2" \| 1) URL parser needs changing.
			\| generally does not work today
	\|-		\|-
	\| http://example.org/test.zip!image.jpg (".zip!" as separator, but request path includes trailing ".zip")		\| http://example.org/test.zip!image.jpg (".zip!" as separator, but request path includes trailing ".zip")
	\| /test.zip!inner.zip%!image.jpg		\| /test.zip!inner.zip!image.jpg
			\| possibility for compatibility-shims
	\|-		\|-
	! fragment		! fragment
Line 33:		Line 36:
	\| - (zip base URL is zip:/.../)		\| - (zip base URL is zip:/.../)
	\| 1) Inner and outer URL for resources. 2) Requires new scheme. 3) Fetch needs to be passed fragment.		\| 1) Inner and outer URL for resources. 2) Requires new scheme. 3) Fetch needs to be passed fragment.
			\|
	\|}		\|}

Annevk: /* URLs */

2013-09-13T14:03:28Z

URLs

← Older revision		Revision as of 14:03, 13 September 2013
Line 2:		Line 2:

	{\| class="wikitable"		{\| class="wikitable"
	\|-		\|-
	! name		! name
	! model		! model
	! example		! example
	! nested zips		! nested zips
	! relative URLs pointing outside zip		! relative URLs pointing outside zip
	\|-		! complexity
	! sub-scheme		\|-
	\| A URL is potentially a stack of URLs, the innermost URL represents the request URL and origin		! sub-scheme
	\| zip:http://example.org/test!image.jpg (last "!" as separator)		\| A URL is potentially a stack of URLs, the innermost URL represents the request URL and origin
	\| zip:zip:/test!inner.zip!image.jpg		\| zip:http://example.org/test!image.jpg (last "!" as separator)
	\| - (zip base URL is zip:/.../)		\| zip:zip:/test!inner.zip!image.jpg
	\|-		\| - (zip base URL is zip:/.../)
	! zip-path		\| 1) URLs become a stack. 2) Zip URL needs its own URL object. 3) URL parser needs changing.
	\| A URL gains a zip-path which is excluded from the request URL, origin computed per usual		\|-
	\| http://example.org/test%!image.jpg ("%!" as separator)		! rowspan="2" \| zip-path
	\| /test%!inner.zip%!image.jpg		\| rowspan="2" \| A URL gains a zip-path which is excluded from the request URL, origin computed per usual
	\| √ (../otherimage.jpg)		\| http://example.org/test%!image.jpg ("%!" as separator)
	\|-		\| /test%!inner.zip%!image.jpg
	~~! zip-path #~~2		\| rowspan="2" \| √ (../otherimage.jpg)
	\| ~~A URL gains a zip~~-~~path which is excluded from the request URL, origin computed per usual~~		\| rowspan="2" \| 1) URL parser needs changing.
	\| http://example.org/test.zip!image.jpg (".zip!" as separator, but request path includes trailing ".zip")		\|-
	\| /test.zip!inner.zip%!image.jpg		\| http://example.org/test.zip!image.jpg (".zip!" as separator, but request path includes trailing ".zip")
	~~\| √ (../otherimage.jpg)~~		\| /test.zip!inner.zip%!image.jpg
	\|-		\|-
	! fragment		! fragment
	\| Fetch is passed fragment as well in case response is application/zip and data needs extracting		\| Fetch is passed fragment as well in case response is application/zip and data needs extracting. Resources from a zip have a zip URL as base.
	\| http://example.org/test#image.jpg		\| http://example.org/test#image.jpg
	\| http://example.org/test#inner.zip!image.jpg (??)		\| http://example.org/test#inner.zip!image.jpg (??)
	\| - (zip base URL is zip:/.../)		\| - (zip base URL is zip:/.../)
	\|}		\| 1) Inner and outer URL for resources. 2) Requires new scheme. 3) Fetch needs to be passed fragment.
			\|}

	While zip-path could support relative addressing outside of a zip, it's not clear whether this is desirable.		While zip-path could support relative addressing outside of a zip, it's not clear whether this is desirable.

Annevk: /* URLs */ add model

2013-09-12T16:42:38Z

URLs: add model

← Older revision		Revision as of 16:42, 12 September 2013
Line 4:		Line 4:
	\|-		\|-
	! name		! name
			! model
	! example		! example
	! nested zips		! nested zips
Line 9:		Line 10:
	\|-		\|-
	! sub-scheme		! sub-scheme
	\| zip:http://example.org/test!image.jpg		\| A URL is potentially a stack of URLs, the innermost URL represents the request URL and origin
			\| zip:http://example.org/test!image.jpg (last "!" as separator)
	\| zip:zip:/test!inner.zip!image.jpg		\| zip:zip:/test!inner.zip!image.jpg
	\| - (zip base URL is zip:/.../)		\| - (zip base URL is zip:/.../)
	\|-		\|-
	! zip-path		! zip-path
			\| A URL gains a zip-path which is excluded from the request URL, origin computed per usual
	\| http://example.org/test%!image.jpg ("%!" as separator)		\| http://example.org/test%!image.jpg ("%!" as separator)
	\| /test%!inner.zip%!image.jpg		\| /test%!inner.zip%!image.jpg
	\| √ ../otherimage.jpg		\| √ (../otherimage.jpg)
	\|-		\|-
	! zip-path #2		! zip-path #2
			\| A URL gains a zip-path which is excluded from the request URL, origin computed per usual
	\| http://example.org/test.zip!image.jpg (".zip!" as separator, but request path includes trailing ".zip")		\| http://example.org/test.zip!image.jpg (".zip!" as separator, but request path includes trailing ".zip")
	\| /test.zip!inner.zip%!image.jpg		\| /test.zip!inner.zip%!image.jpg
	\| √ ../otherimage.jpg		\| √ (../otherimage.jpg)
	\|-		\|-
	! fragment		! fragment
			\| Fetch is passed fragment as well in case response is application/zip and data needs extracting
	\| http://example.org/test#image.jpg		\| http://example.org/test#image.jpg
	\| http://example.org/test#inner.zip!image.jpg (??)		\| http://example.org/test#inner.zip!image.jpg (??)

Annevk: /* URLs */

2013-09-12T16:27:14Z

URLs

← Older revision		Revision as of 16:27, 12 September 2013
Line 6:		Line 6:
	! example		! example
	! nested zips		! nested zips
	! ~~in-~~zip~~-URLs~~		! relative URLs pointing outside zip
	\|-		\|-
	! sub-scheme		! sub-scheme
	\| zip:http://example.org/test!image.jpg		\| zip:http://example.org/test!image.jpg
	\|		\| zip:zip:/test!inner.zip!image.jpg
	\|		\| - (zip base URL is zip:/.../)
	\|-		\|-
	! zip-path		! zip-path
	\| http://example.org/test%!image.jpg ("%!" as separator)		\| http://example.org/test%!image.jpg ("%!" as separator)
	\|		\| /test%!inner.zip%!image.jpg
	\|		\| √ ../otherimage.jpg
	\|-		\|-
	! zip-path #2		! zip-path #2
	\| http://example.org/test.zip!image.jpg (".zip!" as separator)		\| http://example.org/test.zip!image.jpg (".zip!" as separator, but request path includes trailing ".zip")
	\|		\| /test.zip!inner.zip%!image.jpg
	\|		\| √ ../otherimage.jpg
	\|-		\|-
	! fragment ~~+ zip URL~~		! fragment
	\| http://example.org/test#		\| http://example.org/test#image.jpg
	\|		\| http://example.org/test#inner.zip!image.jpg (??)
	\|		\| - (zip base URL is zip:/.../)
	\|}		\|}

			While zip-path could support relative addressing outside of a zip, it's not clear whether this is desirable.

	== Format ==		== Format ==

Annevk: basic setup for comparing zip URL tactics

2013-09-12T16:10:51Z

basic setup for comparing zip URL tactics

@@ Line 1: / Line 1: @@
 For http://fetch.spec.whatwg.org/#zip-archives we need to document the zip format. Either through reference to the PKWARE text, or via a new standard (XKCD-style).
-== Gecko ==
+=== Gecko ===
   baku https://mxr.mozilla.org/mozilla-central/source/dom/file/ArchiveZipEvent.cpp
@@ Line 10: / Line 43: @@
   baku you have an ArchiveZipFile for each file.
-== PKWARE ==
+=== PKWARE ===
 * http://www.pkware.com/documents/casestudies/APPNOTE.TXT

Annevk: added Category:Spec coordination using HotCat

2013-08-30T18:46:12Z

added Category:Spec coordination using HotCat

← Older revision		Revision as of 18:46, 30 August 2013
Line 14:		Line 14:
	* http://www.pkware.com/documents/casestudies/APPNOTE.TXT		* http://www.pkware.com/documents/casestudies/APPNOTE.TXT
	* http://mailman.vse.cz/pipermail/sc34wg1study/2010-November/000082.html		* http://mailman.vse.cz/pipermail/sc34wg1study/2010-November/000082.html

			[[Category:Spec coordination]]

Annevk: /* PKWARE */

2013-08-30T16:25:31Z

PKWARE

← Older revision		Revision as of 16:25, 30 August 2013
Line 12:		Line 12:
	== PKWARE ==		== PKWARE ==

	http://www.pkware.com/documents/casestudies/APPNOTE.TXT		* http://www.pkware.com/documents/casestudies/APPNOTE.TXT
	http://mailman.vse.cz/pipermail/sc34wg1study/2010-November/000082.html		* http://mailman.vse.cz/pipermail/sc34wg1study/2010-November/000082.html