Re: threading: is lock needed in pro_message_available

"Huston" <[email protected]> Sat, 6 Dec 2003 11:26:10 -0700
Newsgroups gmane.network.beep.beepcore.c.general
Message-ID <020601c3bc26$6cba8c90$0100a8c0@zizzing>
Lei,

From what I recall your observations are correct. It would take a bit of
looking to track this down because of how the synchronization/locking was
implemented.

--Huston

----- Original Message ----- 
From: "Lei Zhang" <[email protected]>
To: <[email protected]>
Sent: Thursday, December 04, 2003 12:57 PM
Subject: [Beepcore-c-users] threading: is lock needed in
pro_message_available


> Howdy,
>
> I've been digging the wrapper code to no avail for answer to a simple
> question: it seems each incoming message gets delivered to the
> application via a different thread, should I use lock to protect
> critical section in pro_message_available?  Some testing shows that the
> application gets notified about an incoming message only after it has
> finished sending RPY to the previous message - is this observation wrong?
>
> Any hint is immensely appreciated.
> Lei
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> Does SourceForge.net help you be more productive?  Does it
> help you create better code?  SHARE THE LOVE, and help us help
> YOU!  Click Here: http://sourceforge.net/donate/
> _______________________________________________
> Beepcore-c-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/beepcore-c-users
>
>



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/