[zeromq-dev] Socket connect status

[Diablo 666]

Hi,

> The problem is that each end of the queue lives in a different thread. 
> Writer thread cannot access read end of the queue and vice versa.

This should not be a problem, I guess. The calling thread can see the
current write position, so the positions differ after a write.
Changes in the read positions may be seen with a certain delay, which
means, that the queue may be empty, but the calling thread sees
different write and read positions. It can not happen, that the queue
helds data but the calling thread sees no difference. So this approach
should be save.

Andreas
 		 	   		  
_________________________________________________________________
http://redirect.gimas.net/?n=M1003xHotmail2
Alles in einem Postfach  –  Ich will Hotmail!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20100317/b9a7ca3d/attachment.htm>