Thanks for the explanation. The getURN method is an interesting proposal. It seems useful even when you do have a File because you might want to force the file contents to be loaded as a particular media type.
-Darin On Tue, Mar 23, 2010 at 7:40 PM, Michael Nordman <[email protected]>wrote: > This has been discussed before, not sure what the conclusion was (if any) > http://www.mail-archive.com/[email protected]/msg06137.html > > <http://www.mail-archive.com/[email protected]/msg06345.html><snip> > > In order for the URN to be useful, it would have to have a mediaType > associated with it, and then there's content-disposition to think > about, which then wants a file name as well...boy, that's a lot of > baggage. However, since these aren't really inherent properties of > the Blob, just of the way you want the browser to view the Blob, it > would seem natural to me do to something like this: > > interface Blob { > ... > DOMString getURN(in DOMString mediaType, > [Optional] in DOMString contentDisposition, > [Optional] in DOMString name); > }; > > </snip> > > > On Tue, Mar 23, 2010 at 7:19 PM, Dmitry Titov <[email protected]> wrote: > >> Blob would need a content-type for that, but it could probably easy be >> added as a property that is assignable. >> >> BTW if the Blob could have a urn and mime type, this info could be >> directly used to form the headers for the Blob when sending it in multipart >> form using FormData. >> >> Dmitry >> >> On Tue, Mar 23, 2010 at 2:23 PM, Darin Fisher <[email protected]> wrote: >> >>> Apologies if this has been discussed before, but I'm curious why URN is >>> not a property of Blob. It seems like it would be useful to be able to load >>> a slice of a File. For example, this could be used by an application to >>> fetch all of its subresources out of a single file. >>> >>> -Darin >>> >> >> >
