|
Hi,
I am going through the reSiprocate code and trying
to understand the threading model.
- Can you confirm that the stack is a
single thread. In the architectural diagram (http://svn.resiprocate.org/viewsvn/resiprocate/main/resip/stack/doc/ResipArchitecture.pdf?view=co), it
shows multiple threads (separate threads for transports, Transaction FSM
& SipOject).
- Can we run mutiple TUs on a same stack and
each TUs running as a separate thread?
- DUM threading model (http://www.resiprocate.org/DUM_Threading) states
"A class called DumThread is in the
works. This will allow you to run all of resiprocate in it's own thread (or
threads)". Can some one clarify following understanding is
right.
i. DumThread Class gets a message
from FIFO and processes it in a loop. By having different message filter
rules one can have different threads processing different messages using
multiple DUMThreads.
ii. If we want to have multiple threads
processing different calls (i.e same message filter rules), can this be
achieved with the same DumThread Class??
4. what is the call rate
with the current threading model?
Thanks &
Regards,
Meenatchy Annamalai
Consultant
Prithvi Information Solutions
Ltd
10Q3A1, Cyber Towers
HITEC City, Madhapur
Hyderabad - 500
081
|