-
Notifications
You must be signed in to change notification settings - Fork 15
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
Still working on this? (Also: contact info) #5
Comments
👍 |
@tarcieri agree totally on this!! 👍 |
@Spaceghost the C++ implementation does not expose a C ABI, much less an "FFIable" one (i.e. it doesn't rely on the preprocessor) I am a huge fan of FFI and used it extensively in RbNaCl however someone would need to create an FFIable C ABI to the C++ implementation first. |
👍 |
There's a Ruby GSoC project underway to build a C wrapper around capnproto's C++ implementation and then re-wrap that in FFI. We'll see how it goes. |
Thanks for the update @tarcieri. Sounds promising. |
@tarcieri, would you happen to know how the Ruby GSoC project went? Also progress on making an implementation that works for JRuby? |
@peakxu last year's project didn't go so well, but there's another GSoC effort this year |
@tarcieri any chance you know how 2016 GSoC effort went? |
It went well, I think! It should now support RPC: https://github.com/nemoNoboru/capnp-ruby Perhaps it should be moved to https://github.com/capnproto |
@tarcieri Is it being used in prod? Is anyone actively maintaining it? |
(Not meant to be challenges, I'm just honestly curious.) |
@kentonv not to my knowledge. I'm not sure people are actually aware of it. All that said, I think it's the most complete implementation of capnp in Ruby to date. |
I used it on production during a time but we stopped using capnp entirely because the libs for other languages that we were using were less mature (IIRC go and node) |
I'd love to have a mature Cap'n Proto binding for Ruby! Particularly one that works across CRuby and JRuby.
I was just talking to @kentonv about it, and this approach (MRI cext) seems reasonable for CRuby. I think the JRuby version should bind to capnproto-java, which is unfortunately much less mature than the C++ version and, AFAIK, doesn't support the RPC protocol.
Getting serialization working across both CRuby and JRuby would be a good start.
Have you thought about making a project mailing list?
The text was updated successfully, but these errors were encountered: