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

Investigate using FFI instead of writing C extensions #56

Open
rtyler opened this issue Oct 21, 2014 · 1 comment
Open

Investigate using FFI instead of writing C extensions #56

rtyler opened this issue Oct 21, 2014 · 1 comment
Assignees
Labels

Comments

@rtyler
Copy link
Member

rtyler commented Oct 21, 2014

FFI looks like it has matured enough to where we could delete all the custom C code in this repository and just use FFI bindings.

Couple of open questions:

  1. Retaining Hermann::Result objects through the FFI callbacks support, will that "just work".
  2. Using FFI with static and/or dynamically libraries? What does this mean for the embedded librdkafka

The more we can match the Hermann::Provider::JavaProducer API the better

@jamescway
Copy link
Contributor

  1. here looks like you can pass back complex types, some kind of casting.
#objptr is a struct *
#this is ruby
objptr = MyLibrary.create_object("my object")
  1. not sure, would it require something different to building librdkafka.a in the extconf.rb?

@rtyler rtyler added the MRI label Nov 21, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

2 participants