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

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

From: Aaron Boodman <aa@google.com>
Date: Wed, 27 Aug 2008 14:59:30 -0700
Message-ID: <278fd46c0808271459m316635ecp50c49acf9e3aff2b@mail.gmail.com>
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.

- a
Received on Wednesday, 27 August 2008 14:59:30 UTC

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