[linux-audio-dev] XAP and background processing

[David Olofson]

Correction:
> 'data' is user defined data that is passed to the worker thread.
> Obviously, you should keep your hands off this data until you get
> it back (through XAP_A_WORKER_DONE), since the worker is supposed
> to be running in a different thread.

The <maybe> section should start here, obviously. (Not much point in 
using lock-free FIFOs and stuff if you don't know if you can get a 
background worker at all.)


> You may break this rule if you
> *really* know what you're doing. Lock-free FIFOs and similar
> constructs that are thread safe by design may be shared. Do note,
> however, that hosts are not *required* to actually run worker calls
> in another thread!
>
> <maybe>
> If this doesn't work for you, you must have a hint
> "REQUIRES_WORKER_THREAD" that tells hosts that don't provide
> out-of-thread worker calls to stay away from your plugin.
>
> FIXME:	Plugins that will work in different ways depending on
> 	whether workers are in a separate thread or not, should
> 	probably be able to tell, preferably during instantiation.
> </maybe>


//David Olofson - Programmer, Composer, Open Source Advocate

.- The Return of Audiality! --------------------------------.
| Free/Open Source Audio Engine for use in Games or Studio. |
| RT and off-line synth. Scripting. Sample accurate timing. |
`---------------------------> http://olofson.net/audiality -'
   --- http://olofson.net --- http://www.reologica.se ---