Re: [reSIProcate-users] Threading model

[Byron Campen <bcampen@xxxxxxxxxxxx>]

	You can have multiple threads calling receive, sure. But, unless your  
threads are doing some pretty heavy lifting, having lots of them won't  
be all that advantageous (you'll end up with the stack thread taking  
up one CPU, and a handful of threads doing very little compared to the  
stack thread). Also, if you ever need to correlate an incoming message  
with one received previously, having the incoming stuff randomly  
scattered across multiple threads will probably not work to your  
advantage.

Best regards,
Byron Campen

> So it would be OK then to have the stack thread putting messages in  
> the fifo and multiple PThreads pulling messages out and using the  
> same stack to send replies?
>
>
> Byron Campen wrote:
> >    The StackThread gives cycles to the stack, which causes messages  
> > to be put in a fifo. SipStack::receive() pulls messages out of that  
> > fifo.
> >
> > Best regards,
> > Byron Campen
>
> _______________________________________________
> resiprocate-users mailing list
> resiprocate-users@xxxxxxxxxxxxxxx
> List Archive: http://list.resiprocate.org/archive/resiprocate-users/

Attachment: smime.p7s
Description: S/MIME cryptographic signature