| < Previous by Date | Date Index | Next by Date > |
| < Previous in Thread | Thread Index | Next in Thread > |
Hi all,
I've already read the page about DUM threading and my application uses the Separate DUM and Stack Threads model. That page explains that in this case the application should queue commands to the DUM thread when it wants to call methods on the DUM API, and there are already available commands like provideOfferCommand, provideAnswerCommand and so on.
My question is how can I use those commands if, before calling them, I have to make some checks using the InviteSessionHandle that I stored previously? (e.g isConnected, isAccepted, isTerminated). I think this wouldn’t be thread-safe.
I could not find any examples in resiprocate code base that uses those commands. The dum tests answers directly from the callbacks, repro doesn't implement InviteSessionHandler callsbacks and recon creates its own commands. Should I create my own commands as well? If so, what are the use cases for the commands already provided by resiprocate? Thanks in advance.
Diego
_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@resiprocate.org
https://list.resiprocate.org/mailman/listinfo/resiprocate- devel