> thank you for your answer and the modification of the triggerEvent
> function. Unfortunately I am not completely convinced whether this
> will cure all race conditions which are imaginable for the application
> of the trigger method in a multithreading environment.
I believe it's now OK, as l
Hello Ross,
thank you for your answer and the modification of the triggerEvent
function. Unfortunately I am not completely convinced whether this
will cure all race conditions which are imaginable for the application
of the trigger method in a multithreading environment. I will have to
run some l
Matthias,
Thanks for the note. You've correctly identified a potential race condition
caused by "triggerEvent()" being called by a non-LIVE555 thread. I've now
installed a new version (2012.06.17) that should avoid this problem. The
solution was to no longer have the "triggerEvent()" functio
Hello Ross,
because I am new here let me first express my thankfulness for that great
library which will probably save a huge amount of development time for the
project I am about to evaluate currently.
I read your FAQ and the mailing lists multiple times to not bother you with
trivial questions
