Hi Garret,
Thanks for your reply. I actually found a bug on my side. Nanomsg seems to
be working correctly as expected.
Thanks.
On Thursday, December 31, 2015, FreeLists Mailing List Manager <
ecartis@xxxxxxxxxxxxx> wrote:
nanomsg Digest Thu, 31 Dec 2015 Volume: 04 Issue: 107
In This Issue:
[nanomsg] Re: Multiple paired connections
----------------------------------------------------------------------
From: Garrett D'Amore <garrett@xxxxxxxxxx <javascript:;>>
Subject: [nanomsg] Re: Multiple paired connections
Date: Wed, 30 Dec 2015 23:03:33 -0800
If you aren't backing up TCP then it should work. But PAIR is best effort
delivery unlike req/rep and so it's possible to lose messages due to TCP
flow control.
I'm not sure if this is what is happening - but it might be worth checking.
Sent from my iPhone
On Dec 30, 2015, at 6:54 PM, Roger Floydman <roger.floydman@xxxxxxxxx<javascript:;>> wrote:
between various plugin modules and the main core of the application. The
I have recently been experimenting with nanomsg to allow communication
PAIR protocol seemed to be perfect for my requirements to allow a one to
one communication between the module and the core.
being the server side doing a nn_bind and my module doing a nn_connect.
I have setup the pair using nn_socket ( AF_SP, NN_PAIR ) with my core
6th i receive no messages. There are no error messages coming back from any
It all works great until i get to 5 paired connections and then on the
of the nanomsg calls so i'm a bit stumped.
Should it be possible to have many paired connections? E.g. 100
Thanks.
------------------------------
End of nanomsg Digest V4 #107
*****************************
