Transfer existing keys and leaving features

[lonnietc]

Hello,

I am researching Chord DHT for distributed key-values in Rust and came across your chord-dht project.

I want to learn from it as well as was wondering if you had thoughts about completing the TODO list:

1. Transfer existing keys when node is down or joins the ring
2. Allow node to leave

Also do you have any plans or options on changing the license from AGPL to MIT/BSD or some other so that it can be easier to include as part of larger projects since I could possible see some really good use for it and would not like to rewrite a whole new system from scratch if yours would work well as a library part of the project instead.

Thanks and have a great day

[DCsunset]

Hi,

As for the todo items, it shouldn't be difficult to come up with an idea as they are very basic operations. However, many edge cases must be covered so the implementation might be lengthy and error-prone. I currently don't have plans to do it because I'm busy with other things.

In terms of the license, I choose AGPL in the hope that people reading and modifying my code can also share their code to more people. Are you asking it because you want to use the code in some commercial software? I may also consider other licenses (probably attaching some additional clauses) if you could briefly describe how you want to use it and whether you have plans to open source it.

[lonnietc]

Hello,

Thanks for getting back to me and I am researching for the development of a massively scalable P2P type project and will probably use a Chord DHT K/V store inside it. The project "may" be open source, but not sure, may also be in Rust, Golang, or C/C++, and also may be a library which could be included in commercial efforts either by myself or other users once operational.

I currently have been looking at 2 implementation for a Distributed Chord-DHT K/V store for which one is yours (Rust) and another is in Golang under MIT licensing which gives a lot of flexibility for opensource or commercial implementations.

Although still in the research phase and laying out the design of the project, I figure that I basically have 3 options depending upon some final design decisions that are up in the air, but I have version in Golang and Rust (yours), or I can work in writing one from scratch if needed although I was hoping to not do that so as to reduce the development of the PoC time in the Pre-Alpha work.

Thanks again and have a great day

[DCsunset]

Hi,

After thinking about it, I think I can change the license to LGPL. LGPL is more permissive and you only need to publish your changes to this library under the same license. The remaining part of your program can remain close-sourced as long as you use chord-dht as a shared library.

Let me know if it could meet your needs.

[lonnietc]

Hello @DCsunset and hope that you are doing well today.

I truly appreciate you taking the time to consider my inquiry and for the possibly LGPL switch over, but I do not think that will work for my particular needs as in its current state, the DHT needs a lot of work before it would be ready as a viable shared library and also I did not want to use it as a sharded library but was going to build around it.

Although there is a very high probability that the whole project was going to be open-sourced at some point, initially, it was not going to be this way until it was ready, utilized, and tested a lot down the road.

At this stage, it seems that I will probably just have to write one from scratch or find another viable solution but wanted to Thank You once again.

[DCsunset]

No problem. Sorry that the LGPL isn't working for you as well. I hope you can find your solution (this library isn't very complex so it should be relatively easy to implement your own one)