[zeromq-dev] C++, socket_t, and poll

Martin Sustrik sustrik at 250bpm.com
Wed Oct 27 18:13:37 CEST 2010

On 10/27/2010 05:51 PM, David Hait wrote:
> Yes, but once you receive the notification, and you have the item.socket (which is a void*), how do you cast this back to a socket_t?  There is no constructor for socket_t which takes a void*.
That would mean several socket_t's pointing to the same socket. That in 
turn would require reference counting etc.

It's simple: If you've extracted pollitem no.3 from socket S and then 
you got event on pollitem no.3, it means that the event happened on 
socket S.


More information about the zeromq-dev mailing list