abraxas - npm Package Compare versions

Comparing version 0.2.0 to 0.2.1

client.js

		@@ -179,8 +179,6 @@ "use strict";
		packets.acceptByJob('WORK_STATUS', jobid, function (data) {
		var status = copy(data.args);
		status.complete = Number(status.complete);
		var total = Number(status.total); delete status.total;
		status.complete = total ? status.complete / total : status.complete;
		delete status.total;
		task.emit('status',status);
		var complete = Number(data.args.complete);
		var total = Number(data.args.total);
		var percent = complete = total ? complete / total : complete;
		task.emit('status',percent);
		});
		@@ -187,0 +185,0 @@ var lastWarning;

gearman-rpc.md

		@@ -0,1 +1,4 @@
		*Please note, this is just notes that I've written to myself. They describe
		a hypothetical library built on top of Abraxas. Not something bundled.*

		Gearman is a schemaless job server, with realtime and durable background
		@@ -2,0 +5,0 @@ job execution.

package.json

		@@ -11,3 +11,3 @@ {
		"author": "Rebecca Turner <me@re-becca.org> (http://re-becca.org)",
		"version": "0.2.0",
		"version": "0.2.1",
		"dependencies": {
		@@ -14,0 +14,0 @@ "gearman-packet": "^0.2.1",

README.md

		@@ -165,6 +165,5 @@ Abraxas

		Status updates from the worker will be emitted as `status` events with the
		same arguments as the result of the
		Status updates from the worker will be emitted as `status` events with
		percentage completion as the argument.


		Using a task as a promise will result in the promise being resolved with the
		@@ -171,0 +170,0 @@ concatenated value of the stream. Exceptions and job failures will result

task-worker.js

		@@ -16,6 +16,2 @@ "use strict";
		this.outbound = new stream.PassThrough(options.response);
		delete options.response;
		delete options.jobid;
		delete options.uniqueid;
		delete options.client;
		Task.call(this,payload,this.outbound,options);
		@@ -22,0 +18,0 @@ }

TODO.md

		@@ -1,4 +0,1 @@
		* Option for maximum number of jobs to run at a time per connection. Most
		gearman libraries only allow one per connection, but that's neither a
		limitation of the protocol nor the server. We can handle it trivially.
		* Tests for the client/worker API layer. (The protocol layer is already fully tested.)
		@@ -5,0 +2,0 @@ * The server library, along with a trivial gearman server implementation.

README.md~

Sorry, the diff of this file is not supported yet

New alerts