[whatwg] A slightly different use-case for shared workers

[Robert O'Callahan]

On Thu, Aug 28, 2008 at 9:59 AM, Aaron Boodman <aa at google.com> wrote:

> I encounter sites frequently that want to "pop out" part of their
> application free of the page, into a smaller window. For example,
> Pandora radio (http://pandora.com) does this. The player starts out
> embedded in the normal content area, but users have the option to pop
> it out into a smaller, separate window.
>
> One problem with these apps is that they have to shutdown and restart
> in the popup window. So if I'm playing a song in Pandora, it loses
> tracks of where I am and restarts in the pop out player.
>
> It seems like shared workers could help with this problem. If some
> future version of workers had access to the Audio API, the base
> pandora.com page would start a shared worker, which would be used to
> play the audio. If the user opted to open the "player" in a popup, the
> popup would simply obtain a reference to the existing worker. The
> music wouldn't have to restart. If the user navigated away from
> pandora.com, the popup would keep the worker alive until it was
> closed.
>

Why not just open new window and move the playing <audio> element from the
old window into the new window? You might need to call play() on it again in
the new window, but you shouldn't lose your place in the stream.

Rob
-- 
"He was pierced for our transgressions, he was crushed for our iniquities;
the punishment that brought us peace was upon him, and by his wounds we are
healed. We all, like sheep, have gone astray, each of us has turned to his
own way; and the LORD has laid on him the iniquity of us all." [Isaiah
53:5-6]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20080828/3c587a2b/attachment-0001.htm>