This seems very related to how prefixes/terms are expanded to IRIs in
JSON-LD - see http://www.w3.org/TR/json-ld/#iris
The JSON-LD approach is more like registering new "local" protocols,
as they look like URIs.
If we tried that out, then:
would mean that
would resolve to fred/hello.txt wit
On Tue, May 7, 2013 at 9:29 AM, Robin Berjon wrote:
> Have you looked at just reusing JAR for this (given that you support it in
> some form already)? I wonder how well it works. Off the top of my head I
> see at least two issues:
>
JARs are just ZIPs with Java metadata. We don't need metadata,
* Florian Bösch wrote:
>It can be implemented by a JS library, but the three reasons to let the
>browser provide it are Convenience, speed and integration.
>
>Convenience is the first reason, since browsers by far and large already
>have complete bindings to compression algorithms and archive forma
On Tue, May 7, 2013 at 3:29 PM, Robin Berjon wrote:
> On 06/05/2013 20:42 , Jonas Sicking wrote:
>>
>> The only things that implementations can do that JS can't is:
>> * Implement new protocols. I definitely agree that we should specify a
>> jar: or archive: protocol, but that's orthogonal to whet
* Robin Berjon wrote:
>I wonder if we couldn't have a mechanism that would not require a
>separate URI scheme. Just throwing this against the wall, might be daft:
>
>We add a new relationship: bundle (archive is taken, bikeshed
>later). The href points to the archive, and there can be as many as
On Tue, May 7, 2013 at 7:29 AM, Robin Berjon wrote:
> On 06/05/2013 20:42 , Jonas Sicking wrote:
>>
>> The only things that implementations can do that JS can't is:
>> * Implement new protocols. I definitely agree that we should specify a
>> jar: or archive: protocol, but that's orthogonal to whet
Top-posting FTW!
Smells a bit like declarative navigation controller to me. (No, I don't
say that like it's a bad thing, actually).
cheers
On Tue, 07 May 2013 16:29:49 +0200, Robin Berjon wrote:
On 06/05/2013 20:42 , Jonas Sicking wrote:
The only things that implementations can do that J
On Tue, May 7, 2013 at 11:34 AM, Bjoern Hoehrmann wrote:
> Robin seems to address that in the parts of his mail you didn't quote.
My bad :-(
Have to say it does seem quite elegant. And has great fallback (if
implemented on the server).
--
http://annevankesteren.nl/
* Anne van Kesteren wrote:
>On Tue, May 7, 2013 at 7:29 AM, Robin Berjon wrote:
>> This isn't very different from JAR but it does have the property of more
>> easily enabling a transition. To give an example, say that the page at
>> http://berjon.com/ contains:
>>
>>
>>
>> and
>>
>>
>
>Y
On Tue, May 7, 2013 at 7:29 AM, Robin Berjon wrote:
> This isn't very different from JAR but it does have the property of more
> easily enabling a transition. To give an example, say that the page at
> http://berjon.com/ contains:
>
>
>
> and
>
>
You need a new URL scheme here. Otherwis
On 06/05/2013 20:42 , Jonas Sicking wrote:
The only things that implementations can do that JS can't is:
* Implement new protocols. I definitely agree that we should specify a
jar: or archive: protocol, but that's orthogonal to whether we need an
API.
Have you looked at just reusing JAR for thi
On Tue, May 7, 2013 at 8:09 AM, Jonas Sicking wrote:
> > You're arguing for allowing accessing files inside ZIPs by URL, which
> means
> > you're going to have to do the work anyway, since you'd be able to
> create a
> > blob URL, reference a file inside it using XHR, and get a Blob as a
> result
mpression is pretty orthogonal, implementation-wise, to a
protocol handler for ZIP decompression.
Look, the fact that we need use cases should not be surprising to
people on this mailing list. And I know that it's not surprising to
you. One of the heavy arguments that has been brought up for
On Mon, May 6, 2013 at 8:01 PM, Jonas Sicking wrote:
> On Mon, May 6, 2013 at 5:15 PM, Glenn Maynard wrote:
> > I'm not aware of any optimized inflate implementation in JS to compare
> > against, and it's a complex algorithm, so nobody is likely to jump
> forward
> > to spend a lot of time imple
On Mon, May 6, 2013 at 5:15 PM, Glenn Maynard wrote:
> I'm not aware of any optimized inflate implementation in JS to compare
> against, and it's a complex algorithm, so nobody is likely to jump forward
> to spend a lot of time implementing and heavily optimizing it just to show
> how slow it is.
On Mon, May 6, 2013 at 1:11 PM, Eric U wrote:
> This came up a few years ago; Gregg Tavares explained in [1] that only
> /some/ zipfiles are streamable, and you don't know whether yours are
> or not until you've seen the whole file.
>
> Eric
>
> [1]
> http://lists.w3.org/Archives/Public/publ
; Webapps WG , Charles McCathie Nevile
>> , Andrea Marchesini
>>
>> Subject: Re: ZIP archive API?
>>
>> It can be implemented by a JS library, but the three reasons to let the
>> browser provide it are Convenience, speed and integration.
>>
>> Conv
On Mon, May 6, 2013 at 7:42 PM, Jonas Sicking wrote:
> On Mon, May 6, 2013 at 4:27 AM, Robin Berjon wrote:
>> On 03/05/2013 21:05 , Florian Bösch wrote:
>>>
>>> It can be implemented by a JS library, but the three reasons to let the
>>> browser provide it are Convenience, speed and integration.
>
On Mon, May 6, 2013 at 4:27 AM, Robin Berjon wrote:
> On 03/05/2013 21:05 , Florian Bösch wrote:
>>
>> It can be implemented by a JS library, but the three reasons to let the
>> browser provide it are Convenience, speed and integration.
>
> Also, one of the reasons we compress things is because th
On Mon, May 6, 2013 at 5:03 AM, Glenn Maynard wrote:
> On Mon, May 6, 2013 at 6:27 AM, Robin Berjon wrote:
>>
>> Another question to take into account here is whether this should only be
>> about zip. One of the limitations of zip archives is that they aren't
>> streamable. Without boiling the oc
I second that. Thanks Florian.
On 05/03/2013 02:52 PM, Florian Bösch wrote:
> I'm interested a JS API that does the following:
>
> Unpacking:
> - Receive an archive from a Dataurl, Blob, URL object, File (as in
> filesystem API) or Arraybuffer
> - List its content and metadata
> - Unpack member
On Mon, May 6, 2013 at 6:27 AM, Robin Berjon wrote:
> Another question to take into account here is whether this should only be
> about zip. One of the limitations of zip archives is that they aren't
> streamable. Without boiling the ocean, adding support for a streamable
> format (which I don't
The main reason to use an archive (other than the space-savings) for me is
to be able to transfer tens of thousands of small items that go into
producing WebGL applications of non trivial scope.
On Mon, May 6, 2013 at 1:27 PM, Robin Berjon wrote:
> On 03/05/2013 21:05 , Florian Bösch wrote:
>
>
On 03/05/2013 21:05 , Florian Bösch wrote:
It can be implemented by a JS library, but the three reasons to let the
browser provide it are Convenience, speed and integration.
Also, one of the reasons we compress things is because they're big.*
Unpacking in JS is likely to mean unpacking to memo
On May 3, 2013 4:20 PM, "Charles Pritchard" wrote:
>
> On May 3, 2013, at 3:18 PM, Jonas Sicking wrote:
>
> >> platforms, but it matters a great deal
> >> on underpowered devices such as mobiles.
> >
> > Show me some numbers to back this up and you'll have me convinced :)
> >
> > Remember that on
On May 3, 2013, at 3:18 PM, Jonas Sicking wrote:
>> platforms, but it matters a great deal
>> on underpowered devices such as mobiles.
>
> Show me some numbers to back this up and you'll have me convinced :)
>
> Remember that on underpowered devices native code is proportionally slower
> too.
On Fri, May 3, 2013 at 12:12 PM, Paul Bakaus wrote:
>
>
> From: Florian Bösch
> Date: Fri, 3 May 2013 21:05:17 +0200
> To: Jonas Sicking
> Cc: Paul Bakaus , Anne van Kesteren ,
> Webapps WG , Charles McCathie Nevile
> , Andrea Marchesini
>
> Subject: Re:
es McCathie Nevile
mailto:cha...@yandex-team.ru>>, Andrea Marchesini
mailto:amarches...@mozilla.com>>
Subject: Re: ZIP archive API?
It can be implemented by a JS library, but the three reasons to let the browser
provide it are Convenience, speed and integration.
Convenience is t
6 +0200
>> To: Anne van Kesteren
>> Cc: Paul Bakaus , Charles McCathie Nevile <
>> cha...@yandex-team.ru>, public-webapps WG ,
>> Andrea Marchesini
>> Subject: Re: ZIP archive API?
>>
>> I'm interested a JS API that does the following:
>>
>&g
nne van Kesteren
> Cc: Paul Bakaus , Charles McCathie Nevile <
> cha...@yandex-team.ru>, public-webapps WG , Andrea
> Marchesini
> Subject: Re: ZIP archive API?
>
> I'm interested a JS API that does the following:
>
> Unpacking:
> - Receive an archive from
: Anne van Kesteren mailto:ann...@annevk.nl>>
Cc: Paul Bakaus mailto:pbak...@zynga.com>>, Charles McCathie
Nevile mailto:cha...@yandex-team.ru>>, public-webapps WG
mailto:public-webapps@w3.org>>, Andrea Marchesini
mailto:amarches...@mozilla.com>>
Subject: Re: ZIP a
I'm interested a JS API that does the following:
Unpacking:
- Receive an archive from a Dataurl, Blob, URL object, File (as in
filesystem API) or Arraybuffer
- List its content and metadata
- Unpack members to Dataurl, Blob, URL object, File or Arraybuffer
Packing:
- Create an archive
- Put in me
On Thu, May 2, 2013 at 1:15 AM, Paul Bakaus wrote:
> Still waiting for it as well. I think it'd be very useful to transfer sets
> of assets etc.
Do you have anything in particular you'd like to see happen first?
It's pretty clear we should expose more here, but as with all things
we should do it
On 03/05/2013 13:40 , Arthur Barstow wrote:
Other than Mozilla, is there any other implementor interest?
I'm wondering if steering this work to a CG would be `best` for now,
especially if no one steps up to be Editor.
I think that this is useful and I would rather it were inside a group
than
nl>>
Cc: Charles McCathie Nevile <mailto:cha...@yandex-team.ru>>, public-webapps WG
mailto:public-webapps@w3.org>>, Andrea
Marchesini mailto:amarches...@mozilla.com>>,
Paul Bakaus mailto:pbak...@zynga.com>>
Subject: Re: ZIP archive API?
I am very interested in
team.ru>>, public-webapps WG
mailto:public-webapps@w3.org>>, Andrea Marchesini
mailto:amarches...@mozilla.com>>, Paul Bakaus
mailto:pbak...@zynga.com>>
Subject: Re: ZIP archive API?
I am very interested in working with archives. I'm currently using it as a
delivery fro
I am very interested in working with archives. I'm currently using it as a
delivery from server (like quake packs), import and export format for WebGL
apps.
On Tue, Apr 30, 2013 at 3:18 PM, Anne van Kesteren wrote:
> On Tue, Apr 30, 2013 at 1:07 PM, Charles McCathie Nevile
> wrote:
> > Hi all,
On Tue, Apr 30, 2013 at 1:07 PM, Charles McCathie Nevile
wrote:
> Hi all, at the last TPAC there was discussion of a ZIP archive proposal.
> This has come and gone in various guises.
>
> Are there people currently interested in being able to work with ZIP in a
> web app? Are there implementors and
Hi all, at the last TPAC there was discussion of a ZIP archive proposal.
This has come and gone in various guises.
Are there people currently interested in being able to work with ZIP in a
web app? Are there implementors and is there an editor?
cheers
Chaals
--
Charles McCathie Nevile - C
39 matches
Mail list logo
