W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2011

Re: [FileAPI] Length of the opaque string for blob URLs

From: Arun Ranganathan <aranganathan@mozilla.com>
Date: Fri, 16 Dec 2011 22:11:12 -0800 (PST)
To: Jonas Sicking <jonas@sicking.cc>
Cc: Charles Pritchard <chuck@jumis.com>, Jarred Nicholls <jarred@webkit.org>, public-webapps@w3.org, Michael Nordman <michaeln@google.com>
Message-ID: <1199979716.96957.1324102272953.JavaMail.root@zimbra1.shared.sjc1.mozilla.com>


----- Original Message -----
> On Fri, Dec 16, 2011 at 3:13 PM, Michael Nordman <michaeln@google.com>
> wrote:
> > There is no requirement for that in the spec/draft, it's useful for
> > our
> > implementation.
> 
> I suspect this will be true in Firefox too in due time. So I
> definitely think that we should allow for this.

Oh, just to be 100% clear: the spec as written *now* more than allows for it.  It mandates that the string be *at least* 36 chars, thus allowing for "origin tagging" on top of the existing 36 chars (as Michael Nordman explains it).

What Adrian wants is for the length requirement to be relaxed, so that it can be *less* than 36 chars.  Adrian: is there any reason why MSFT can't use UUID anyway?

-- A*
Received on Saturday, 17 December 2011 06:11:49 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:49 GMT