That’s because nanomsg runs the connect in the background. There is no API
currently available that offers what you want in libnanomsg. The follow up NNG
project *does* have this capability with an API I call “pipe events”.
Garrett
From: Mamuka Sakhelashvili
Sent: Tuesday, January 8, 2019 6:22 AM
To: nanomsg@xxxxxxxxxxxxx
Subject: [nanomsg] Re: Socket stuck on send
More info:
on the server side nn_bind calls, as well ass on the client side nn_connect
calls all return 1. So they succeed. But in real there is no connection
established it seems. How can I identify that there is a connection established
between the client and a server?
On Tue, Dec 25, 2018 at 8:40 PM Mamuka Sakhelashvili
<mamuka.sakhelashvili@xxxxxxxx> wrote:
I have client/server application which shared 4 different sockets:
client: server:
REQ ------------------- REP
SUB ------------------- PUB
PULL -------------------- PUSH
PUSH -------------------- PULL
But the last one, where client pushes and the server pulls, gets stuck on
nn_send call from the client side. I checked and I initialize and connect those
sockets the same way I do for the others. Can there be any reason, like socket
number limit, which might have caused the problem?
Regards,
Mamuka
