-
Notifications
You must be signed in to change notification settings - Fork 105
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
Project Status? #181
Comments
Interested in this as well |
This is still maintained; however the release is limited for now. If you've got any change requiring reviews, feel free to ping me. Of course releases will be made when needed. Priority is still the issues we raised already and incremental changes are definitely welcomed. |
Quick ping on this -- happy to help, and if needed be a temporary maintainer to assist with landing some of the patches. |
@mmastrac I'll get you added in so you can help with maintenance. Let's get this crate shipped! |
Closing as the project has new life and a new release. @mxplusb please open a new issue for QUIC. You may want to weigh in on the QUIC issue in libzmq: zeromq/libzmq#3988 |
Hi, love this port of the C++ code!
Looking at the disclaimer, it sounds like there's quite a bit left to go to get things close to the specification. I'm evaluating a rewrite of one of my projects into Rust, but that means I lose embedded NATS. I'm considering ZeroMQ, and this port is of particular interest because it's native Rust, so no C/C++ bindings. I'd be interested in contributing to this port to bring it up to spec, but I would want to implement a QUIC-based socket provider as part of the contribution.
Is there interest in further contributions, and what is the current status of this port?
The text was updated successfully, but these errors were encountered: