[omniORB] SocketCollection bug

Kevin Bailey ke-omniorb at retriever.dyndns.org
Tue Jan 19 08:46:41 GMT 2010


On Tue, Jan 19, 2010 at 09:08:42AM +0000, Duncan Grisby wrote:
> 
> It would certainly be bad to
> have two threads doing recv() on the same socket, but select() doesn't
> consume any data, so it shouldn't prevent recv() from returning.

Forgive me for jumping in, but I'd like to make sure I
understand omniorb thread model. select() doesn't
consume but won't it typically be followed by its own
recv() and, if the other thread exhausted the socket,
wouldn't this one block ?



More information about the omniORB-list mailing list