[reSIProcate] reSIP Process model

[Byron Campen]

	The stack itself is a single thread. Each TransactionUser (TU) can  
also be a separate thread. DUM is an example of a TU, repro is  
another example (see Proxy.[hc]xx).

Best regards,
Byron Campen

> Hi,
>
>
> I am going through the reSIProcate code. I have a doubt about the  
> stacks process model.
>
> The wiki pages say that the FIFOs in reSIP are used to communicate  
> between threads; however, I could not find any thread other than  
> SipThread within reSIP.
>
> Am I missing something here? Can someone help let me know about the  
> process or thread model of reSIP?
>
>
> Thanks,
>
> Rishin
>
>
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel at list.sipfoundry.org
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20061107/fb456493/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2369 bytes
Desc: not available
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20061107/fb456493/attachment.bin>