Re: [reSIProcate] DumThread

["hanan aboudalal" <hanan.aboudalal@xxxxxxxxx>]

This is the same code that is used in BasicCall.cxx file. You can see that UAC and UAS both belong to the same thread and this is not the case in practical application. There should be a way to use DUM where UAS and UAC are two different excecutables (threads). Please any one have the answer?

On 4/10/06, Suresh Rangaswamy <suresh@xxxxxxxxx> wrote:

Hi All

I have the same question and how does this compare against the code snippet in the documentation.

 

 

 

while (!dumShutDown)

  {

     FdSet fdset;

     stack->buildFdSet(fdset);

     int err = fdset.selectMilliSeconds(stack->getTimeTillNextProcessMS());

     assert ( err != -1 );

     stack->process(fdset);

     while(dumUas->process());

  }

 

Thanks

Suresh

 

 

---

From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx ]
Sent: Monday, April 10, 2006 3:27 PM
To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
Subject: [reSIProcate] DumThread

 

Hi all:

 

What is the role of   resip:: DumThread and  resip::StackThread?  How can they be used? Are they helpful if I want the UAC to be in a thread and UAS to be in another thread? Please don't ignore my questions coz i realy need the answers as soon as possible.

 

best regards,

_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxxxxxx
https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel