mghlarsen / zht Goto Github PK

Add Heartbeat broadcast and monitoring to judge as to peer activity and connectivity.

Implement a synchronized entry datatype.

Implement a basic Bucket Balancing scheme (something better than every peer holding a copy of every bucket).

Add data persistence abilities and peer restart.

Make sets a possible data type for entries.

Implement Caching of Lookups including watching for updates of cached keys.

The ZHT code is undocumented. Also, the speculative documentation could use some refining.

• Document current ZHT code
• Convert all existing docs to reStructured Text
• Find a good solution for properly generating pretty documentation

It would be nice to have a nice way of controlling all the debug messages that are printed (also, it would be nice to have those around for when unexpected stuff happens).

ZHT is woefully untested... since the whole thing is still pretty small, cover everything with test cases.

Before ZHT can be made public, a licensing decision needs to be made official.

• Add LICENSE file, have it included in the generated documentation.
• Add AUTHORS file.
• Add copyright notice to source files.

Add support for multiple tablespaces existing and protocol handling of updates and queries across multiple tablespaces.

Add security features including authentication/authorization, integrity and confidentitality.

The current protocol makes heavy use of ZMQ multipart messages. This should be converted to use protocol buffers. The idea here is that it provides message format versioning automatically, and that it's fast and compact. Some parts of the wire protocol will still need to consist of strings (the header for PUB messages, for instance), but the rest will not and should be converted.

Being able to extract information from remote nodes is a necessary prerequisite for bucket balancing. For now, have the shell implement a rget command which will make a request to the a peer that owns the bucket for that key.

Change ZHT to automatically connect to other known peers rather than requiring manual intervention.

The README needs to be fleshed out.

Change to allow configuration by file instead of solely by command line options.

Change core request engine to handle making multiple concurrent requests to the same peer.

Change ZHT control information to be a implemented as a synchronized tablespace.

The config module is missing test coverage.