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

Status of development #2

Open
benoitc opened this issue Feb 22, 2015 · 3 comments
Open

Status of development #2

benoitc opened this issue Feb 22, 2015 · 3 comments

Comments

@benoitc
Copy link

benoitc commented Feb 22, 2015

I am wondering what is the status of the library? Do you still plan to maintain it?

@kaos
Copy link
Owner

kaos commented Feb 22, 2015

Hi Benoit,

I have plans for it and would like to, but not the time. I would need to use it in a real project to drive the development of it..

@yurrriq
Copy link

yurrriq commented Jan 16, 2016

I'm having some issues with Protocol Buffers and am considering this for a real project.

Are there any caveats I should be aware of before attempting to use this library in production? If we end up using it, I could help maintain.

@kaos
Copy link
Owner

kaos commented Jan 18, 2016

Hi Eric,

You're more than welcome to use it, and help maintain it.

I haven't been able to keep it up to date, so there may be things that need fixing in order to work with recent versions of capnp.

Also, thus far, the api exposed is like the dynamic api of the C++ implementation from capnp. I've been pondering on a static version for the api as well, but haven't come to any conclusions yet.

The RPC stuff is far from complete, nor in any kind of final shape.. but for encoding/decoding messages it should be fine at least.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants