W3C home > Mailing lists > Public > whatwg@whatwg.org > August 2011

[whatwg] createObjectURL(stream) protocol issue

From: Tommy Widenflycht <tommyw@google.com>
Date: Fri, 12 Aug 2011 11:33:22 +0200
Message-ID: <CALLKCfNLjtMveTK77SWH6tbJGUJB0Nv9VztmjLQRY=Tb7Z=F-g@mail.gmail.com>
Imho conceptually streamed media is not the same as data from a file and
thus should be separated. Specifically the code for the video tag for
example now has to ask around what this URL actually points to before taking
action.

/Tommy

On Thu, Aug 11, 2011 at 22:08, Ian Hickson <ian at hixie.ch> wrote:

> On Thu, 11 Aug 2011, Tommy Widenflycht (?~[~O?~Z??~[~X?~[~X?~Z?) wrote:
> >
> > Would it be possible to give the associated URL for a mediastream to
> > have its own protocol, for example mediastream:, instead of the proposed
> > blob:?
> >
> > window . URL . createObjectURL(stream)
> > Mints a Blob URL to refer to the given MediaStream.
> >
> > This would tremendously help the implementation.
>
> Could you elaborate? In what sense does it impact the implementation?
>
> --
> Ian Hickson               U+1047E                )\._.,--....,'``.    fL
> http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
> Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'




-- 
Tommy Widenflycht, Senior Software Engineer
Google Sweden AB, Kungsbron 2, SE-11122 Stockholm, Sweden
Org. nr. 556656-6880
And yes, I have to include the above in every outgoing email according to EU
law.
Received on Friday, 12 August 2011 02:33:22 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:35 UTC