Nanomsg hides the connection away from the user and you have to consider the semantics of the scalability protocol you're using instead. Different transports have to work the same and if you're using IPC or inproc there's no "connection". Why do you need to identify the connection? Couldn't you simply identify who is the peer and include the identifier in each message? Achille Roussel +1 415 490 6339 > On Oct 20, 2014, at 11:26 PM, Ramesh Ramachandran <rameshrg22@xxxxxxxxx> > wrote: > > Hi Team, > > I want to know how to differentiate the connections in nanomsg. > I need to map each connection with some connection ID/String. > Please help me on this. > >> On Mon, Oct 20, 2014 at 5:14 PM, Ramesh Ramachandran <rameshrg22@xxxxxxxxx> >> wrote: >> Hello Team, >> >> Am new to NANOMSG am using >> >> nn_socket(AF_SP, NN_PAIR) sockets. >> >> I want to know how to get the unexpected connection termination event in >> nanomsg sockets. >> >> Like ctrl+c event or kill the client by kill command or crash on client >> side. In this case there is no nn_close(). So how to identify the socket has >> been closed on the other side. >> >> >> >> -- >> With regards >> Ramesh.R > > > > -- > With regards > Ramesh.R