You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 12, 2018. It is now read-only.
Still in the middle of writing the nanomsg implementation, but you can see how I've moved Kafka into it's own plugin under src/transport.
This is kind of a significant refactor, and I was just wondering what the level of desire would be to merge such changes back in? I'd be willing to work to make that happen, but if there's no desire to merge then I could simplify the design by removing layers of queueing/threading that are redundant with nanomsg.
Just want to feel out the current maintainers' thoughts on whether this transport abstraction would be of value to the project.
Thanks.
The text was updated successfully, but these errors were encountered:
Problem: I don't want to setup/maintain a kafka cluster.
Solution: I'm writing in support for nanomsg in a fork:
https://github.com/bitmage/zdb
Still in the middle of writing the nanomsg implementation, but you can see how I've moved Kafka into it's own plugin under
src/transport
.This is kind of a significant refactor, and I was just wondering what the level of desire would be to merge such changes back in? I'd be willing to work to make that happen, but if there's no desire to merge then I could simplify the design by removing layers of queueing/threading that are redundant with nanomsg.
Just want to feel out the current maintainers' thoughts on whether this transport abstraction would be of value to the project.
Thanks.
The text was updated successfully, but these errors were encountered: