RE: [reSIProcate] Thread Question
This should never happen. The dum process call should only be called
from one thread and the onOffer and onConnected callbacks are serial.
> -----Original Message-----
> From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:resiprocate-
> devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Glenn MacGregor
> Sent: Thursday, May 11, 2006 3:02 PM
> To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> Subject: [reSIProcate] Thread Question
>
> Hi All,
>
> I am having, what I think is a threading issue. I defined the virtual
> OnOffer
> and the virtual OnConnected functions in my application.
>
> The OnOffer calls serverSession->accept() at the top of the function
but
> does
> more work in that function including adding the "call" to a map. The
> OnConnected
> looks in the map to find that call.
>
> I have debug where I add the call and where I try to find it, I am
seeing
> that I
> get into OnConnected before I finish OnOffer.
>
> Is there anyway to get the threadid oif the thread running that
function
> so I
> can priont that in debug?
>
> Thanks
>
> Glenn
>
> Glenn MacGregor
> HighStreet Networks
>
> -------------------------------------------------
> This mail sent through IMP: http://horde.org/imp/
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel