Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use newest api from ffi-rzmq #23

Closed
paneq opened this issue Jul 17, 2012 · 4 comments
Closed

Use newest api from ffi-rzmq #23

paneq opened this issue Jul 17, 2012 · 4 comments
Labels

Comments

@paneq
Copy link
Collaborator

paneq commented Jul 17, 2012

Breaking API Change from 0.9.3 to 0.9.5

The 0mq library functions zmq_send() and zmq_recv()
were changed to zmq_sendmsg() and zmq_recvmsg(
with the 0mq 3.x API change. I have changed the bindin
to always use #sendmsg and #recvmsg. This breaks
existing code. This should be the last breaking change
heading into the 1.0 release of these bindings.

chuckremes/ffi-rzmq#56

@mostlyobvious
Copy link
Collaborator

Libraries should have lesser restrictions on gem versions. We can implement strategies for different ffi-rzmq APIs.

@perplexes
Copy link
Owner

Can we detect which version of a particular gem is loaded at runtime?

@mostlyobvious
Copy link
Collaborator

@perplexes most of gems follows this policy: ruby -rffi-rzmq/version -e 'puts ZMQ::VERSION'

@paneq
Copy link
Collaborator Author

paneq commented Nov 2, 2012

We do not use sendmsg and recvmsg methods from the binding itself. We relay on recv_string and send_string which were not changed between versions.

@paneq paneq closed this as completed Nov 2, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants