[Openal-devel] last call: ALC_EXT_disconnect

[Chris Robinson]

On Wednesday 19 August 2009 6:19:05 am E. Wing wrote:
> I also wanted to put this idea out there. What do people think of
> having a callback function you can define (via function pointers) to
> handle device changes? It seems that constantly polling for a device
> change is awkward at best. I know OpenAL doesn't have any event
> callbacks, but maybe looking forward to future revisions, maybe this
> is desirable.

Normally I wouldn't be for callbacks. However, as long as it's restricted to 
the system-level ALC API it may not be that bad. Only concern I would have is 
what kind of execution context could be said about the callback? Could it be 
in a real system-level interrupt (rest of the app is stopped)? A background 
thread (eg. the mixer)? The "main" thread (where the last app call to AL 
occurred)? And what about blocking and re-entrancy, given OpenAL's thread-
safety?