clusterluck - npm Package Compare versions

Comparing version 1.1.1 to 1.1.3

bin/cli.js

		@@ -87,3 +87,3 @@ #!/usr/local/bin/node
		}
		cb(new Error("TODO"));
		cb(new Error("Disconnected from server."));
		return this;
		@@ -107,3 +107,3 @@ }
		this._rcv.flush().forEach((el) => {
		el.cb(new Error("TODO"));
		el.cb(new Error("Disconnected from server."));
		});
		@@ -110,0 +110,0 @@ this.emit("disconnect");

package.json

		{
		"name": "clusterluck",
		"version": "1.1.1",
		"version": "1.1.3",
		"description": "Distributed systems library for gossip protocols, consistent hash rings, and vector clocks.",
		@@ -5,0 +5,0 @@ "main": "index.js",

README.md

		@@ -303,7 +303,7 @@ Clusterluck
		Subsequently, if as a result two nodes are meeting for the first time, a ring merge will occur.
		The resulting state will be gossiped around the cluster, eventually resulting in every node thinking the input node no longer belongs in the cluster.
		The resulting state will be gossiped around the cluster, eventually resulting in every node thinking the input node belongs in the cluster.
		For example, given the previous setup:

		```
		> meet bar
		> meet bar localhost 7023
		{ ok: true }
		@@ -338,3 +338,3 @@
		This command will tell the targeted node by this session to insert a node into its cluster (as it currently views it).
		Subsequently, this information will be gossiped around the cluster, eventually resulting in every node thinking the input node no longer belongs in the cluster.
		Subsequently, this information will be gossiped around the cluster, eventually resulting in every node thinking the input node belongs in the cluster.
		This differs from `meet` in that insertions are not transitive between nodes; it's a new event on the ring state, and therefore overriding when state conflicts occur between nodes sharing ring history.
		@@ -463,4 +463,8 @@ For example:

		- 1.1.3:
		- README fixes for command descriptions.
		- 1.1.2:
		- Remove TODOs from bin/cli.
		- 1.1.1:
		- Grammatical fixes to README
		- Grammatical fixes to README.
		- 1.1.0:
		@@ -471,3 +475,3 @@ - Add timeouts on GenServer request streams.
		- Dawn of time (unversioned up to 1.0.0):
		- Check the commit history for details (about code changes, dawn of time undocumented)
		- Check the commit history for details (about code changes, dawn of time undocumented).

		@@ -478,4 +482,4 @@ ### <a name="TODO"></a>TODO
		- Provide listener for permanent close on connection between two nodes (`maxRetries` option on kernel creation).
		- Add a GenStream class similar to GenServer, but strictly uses streams for communication instead of JS natives (will also require a protocol definition for indicating stream start, etc)
		- Discuss making disconnects between nodes on a node departure forceful or not (it's forceful right now)
		- Add a GenStream class similar to GenServer, but strictly uses streams for communication instead of JS natives (will also require a protocol definition for indicating stream start, etc).
		- Discuss making disconnects between nodes on a node departure forceful or not (it's forceful right now).
		- A distributed lock manager, most likely using the [Redlock algorithm](https://redis.io/topics/distlock), given how well it fits into the current architecture of clusterluck.

clusterluck - npm Package Compare versions

New alerts

Fixed alerts

Improved metrics