[nanomsg] Re: Surveyor Socket and Current Connection Count

  • From: Andrew Starks <andrew.starks@xxxxxxxx>
  • To: "nanomsg@xxxxxxxxxxxxx" <nanomsg@xxxxxxxxxxxxx>
  • Date: Tue, 14 Jan 2014 05:18:20 -0600

On Tuesday, January 14, 2014, Martin Sustrik wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi Andrew,
>
> > 2: I can see that the number of connections is tracked (obviously
> > it must be tracked, on some level). Would extending the survey
> > socket to include a connected_sockets_count property be ill
> > advised?
>
> The problem is that it won't work. Even if you know the number of
> connections, you have no guarantee that some of them won't go away
> while you  are waiting for acks or that some peers aren't hung-up and
> will never send an ack. The timeout is the only reliable way to handle
> the responses.
>
> > 3: Should I just go with the approach that I'm taking?
>
> I would strongly advise not to, but, of course, if you insist on
> shooting yourself in the foot, modifying the library to expose the
> number of connections should be relatively easy :)
>
>
By "the path that I'm on," it was meant that I would do a seperate
handshake with the filter, using a seperate message and not modify the
library. By my reading and with the caveat that you aren't staring at my
source code, I'll interpret this as having your blessing!

Thank you! :)

-Andrew

> Martin
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQEcBAEBAgAGBQJS1PI6AAoJENTpVjxCNN9Y5kwH/3stjMgrr3oQDVBw+v0Edp/2
> ctC0mldyUAdLKRwWJmNAlK0xKnZXAqDOSXd0V9rpat3i7XlQ9m4NOSEC5Tbnatnl
> zmniRVSaKpRkZOQn0JfhbsJQjSQFyraeLFzg9MHkxHV3NESUV++vWDrGfyAamKGt
> d+sCUf80y8s8tZL99s6B8xd4o58ajWhjomKa6l7ja53sgq9vwDOnXN8SPXKSt8KQ
> 5myVorX/+1ytMZdU3qzaYRiCQcBI8krFEAdv3IslTa92oCI6C9osieXSUrilMRfA
> mSjpobCRK6Z/wRcHuINp56kKktHLBCToIotd9yiy5qjqNUgNmTa972ool02sfpY=
> =ezoE
> -----END PGP SIGNATURE-----
>
>

Other related posts: