[reSIProcate] dum-based client instability - Application Time r not thread safe

[Scott Godin]

That's true for the stack methods - but a DUM user must ensure DUM methods
are never call concurrently from 2 different threads.

-----Original Message-----
From: Jason Fischl [mailto:jason at purplecomm.com] 
Sent: Monday, November 01, 2004 1:07 PM
To: Scott Godin
Cc: 'Resiprocate'
Subject: Re: [reSIProcate] dum-based client instability - Application Time r
not thread safe

Scott Godin wrote:

>Oops - never mind - my app and other must protect calls to send / process
>from different threads anyway - so it shouldn't really be a concern.
Sorry.
>
>  
>
You don't need to protect calls to any of these methods. The mutexing is 
done in the Fifos.

Jason