issue with dependency cppnanomsg

[sburke56]

A while ago you posted an issue to the cppnanomsg package that is a c++ bindings package for nanomsg. It looks like that was around the time of creating this proof of concept. Do you know how this was resolved since the line of code that you reference as being the problem is gone in the proof of concept.

I'm looking at using this proof of concept so I'm trying to determine if I'm going to have issues going forward or not.

Hi:
I am trying to make a proof-of-concept RPC with nanomsg and google protobuf.
The shutdown always gives EINVAL, what am I doing wrong ?

[sroycode]

I ended up switching back to zeromq ... in my view nanomsg is nowhere near production ready even now

[sburke56]

Ha do you remember why?

On Sat, Jul 9, 2016, 2:02 AM S R C [email protected] wrote:

Closed #1 #1.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#1 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/AANL43kSBNqfHrdAos7Am9E2BMjRExBQks5qTzl9gaJpZM4JIXvK
.

[sroycode]

The issue was with graceful closure , when I attempted to shutdown by interrupt the program would always crash ( forgot the exact error message) which was traced to a C nn_close() returning EINVAL . Since my project required graceful closure on interrupt this was a no-show.
( Just as an aside , there was a very similar bug in zeromq proxy )

[sburke56]

Thanks for the info.

On Sat, Jul 9, 2016, 3:12 AM S R C [email protected] wrote:

The issue was with graceful closure , when I attempted to shutdown by
interrupt the program would always crash ( forgot the exact error message)
which was traced to a C nn_close() returning EINVAL . Since my project
required graceful closure on interrupt this was a no-show.
( Just as an aside , there was a very similar bug in zeromq proxy )

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#1 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/AANL41WZfTEieWVvWtICy5QkNY0RhJmKks5qT0nZgaJpZM4JIXvK
.

[kuncao]

@sroycode @sburke56
I reproduced the issue
the detail is in
nanomsg/cppnanomsg#2