Re: Web Workers

On Tue, Mar 13, 2012 at 1:38 PM, Jussi Kalliokoski <
jussi.kalliokoski@gmail.com> wrote:

> To come back to the subject of doing audio processing outside workers, I
> was almost convinced that it's OK to force people to use a worker for it,
> because it's a good practice. But then I realized that if we do so, we make
> a few use cases inherently harder. The person writing the code that
> interfaces with the Audio API may not have the luxury of choice in the
> matter. A few examples:
>
>  * A game console emulator. If the console runs everything in a single
> thread, you're going to be in serious trouble if you're trying to isolate
> the audio processing into a separate thread. Game console emulation is hard
> enough as it is.
>  * We mustn't forget that the web is increasingly becoming a compilation
> target, so the code running may be a port of existing code designed for a
> completely different environment.
>

Is postMessaging your samples to a Worker for playback a problem for either
of those cases?

Rob
-- 
“You have heard that it was said, ‘Love your neighbor and hate your enemy.’
But I tell you, love your enemies and pray for those who persecute you,
that you may be children of your Father in heaven. ... If you love those
who love you, what reward will you get? Are not even the tax collectors
doing that? And if you greet only your own people, what are you doing more
than others?" [Matthew 5:43-47]