[reSIProcate] Question on thread-safeness of SipStack::Proces s

[Jason Fischl]

The design assumes that only one thread will be calling process on the 
TransactionController. Changing this is non-trivial.

Jason

Elizabeth Clark wrote:
> I should clarify - I'm referring to multiple threads acting as the
> processing thread.  
> 
> Elizabeth.
> 
> -----Original Message-----
> From: kaiduan xie [mailto:kaiduanx at yahoo.ca] 
> Sent: Wednesday, November 03, 2004 2:39 PM
> To: Elizabeth Clark; 'resiprocate-devel at list.sipfoundry.org'
> Subject: Re: [reSIProcate] Question on thread-safeness of SipStack::Process
> 
> 
> TransactionMaps are only accessed from the transaction processing thread,
> there is no need to protect it with mutex.
> 
> kaiduan
> 
>  --- Elizabeth Clark
> <elizabeth.clark at bridgewatersystems.com> wrote: 
> 
>>Hello,
>>I saw some discussion on the TimerQueue and
>>thread-safety. I've been looking
>>at version 0.4.0 and it seems to me that there is
>>also an a thread-safety
>>issue with the TransactionMaps owned by the TransactionController.  It
>>appears to me that these maps are not accessed using
>>mutexes.
>>Can anyone comment?
>>thanks,
>>Elizabeth
>>
>>>_______________________________________________
>>
>>resiprocate-devel mailing list resiprocate-devel at list.sipfoundry.org
>>
> 
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel 
> 
> ______________________________________________________________________ 
> Post your free ad now! http://personals.yahoo.ca
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel at list.sipfoundry.org
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel