[reSIProcate] reSIP Process model

[Scott Godin]

There is some info here:  

http://wiki.resiprocate.org/wiki/index.php?title=DUM_Threading

http://wiki.resiprocate.org/wiki/index.php?title=FAQ#How_does_the_buildF
dSet.2C_select.2C_process_loop_work.3F

 

The current design allows the stack to run in it's own thread (examples
are InterruptableStackThread and StackThread) and the tu's to run in
their own threads (an example is DumThread).  Threading on the
transports is not currently supported.

 

Scott

 

From: resiprocate-devel-bounces at list.sipfoundry.org
[mailto:resiprocate-devel-bounces at list.sipfoundry.org] On Behalf Of
Rishin Chakraborty
Sent: Tuesday, November 07, 2006 3:18 AM
To: resiprocate-devel at list.sipfoundry.org
Subject: [reSIProcate] reSIP Process model

 

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

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20061107/0e96f261/attachment.htm>