Fivebeans - История изменений

imported>Supportadmin в 17:59, 11 мая 2014

2014-05-11T17:59:22Z

← Предыдущая версия		Версия от 20:59, 11 мая 2014
Строка 1:		Строка 1:
	beanstalkd client & worker daemon for node		beanstalkd client & worker daemon for node

	[https://www.npmjs.org/package/fivebeans оригинал]		[https://www.npmjs.org/package/fivebeans оригинал][https://github.com/ceejbot/fivebeans GitHub]

	==FiveBeansClient==		==FiveBeansClient==

2014-05-11T15:39:41Z

Configuration file

← Предыдущая версия		Версия от 18:39, 11 мая 2014
Строка 366:		Строка 366:

	===Configuration file===		===Configuration file===

			Here's an example yaml configuration:

			<nowiki>beanstalkd:
			host: "127.0.0.1"
			port: 11300
			watch:
			- 'circle'
			- 'picadilly'
			- 'northern'
			- 'central'
			handlers:
			- "./handlers/holborn.js"
			- "./handlers/greenpark.js"
			- "./handlers/knightsbridge.js"
			ignoreDefault: true
			beanstalkd: where to connect
			watch: a list of tubes to watch.
			handlers: a list of handler files to require
			ignoreDefault: true if this worker should ignore the default tube
			</nowiki>

			If the handler paths don't start with / the current working directory will be prepended to them before they are required.

			Why yaml not json? Because when I originally wrote this, it was in support of a ruby service, and yaml is the native config format over in that land. I continue using it because it's more readable than json and easier for humans to type.

2014-05-11T15:38:33Z

bin/beanworker

@@ Строка 343: / Строка 343: @@
 runner.go();</nowiki>
 ===bin/beanworker===
 ===Configuration file===

2014-05-11T15:37:49Z

FiveBeansRunner

← Предыдущая версия		Версия от 18:37, 11 мая 2014
Строка 335:		Строка 335:

	==FiveBeansRunner==		==FiveBeansRunner==
			A wrapper that runs a single beanstalkd worker as a daemon. Responds to the USR2 signal by reloading the configuration and restarting the worker. Handles SIGINT, SIGHUP, and SIGQUIT by completing processing on the current job then stopping.

			Example use:

			<nowiki>var fivebeans = require('fivebeans');
			var runner = new fivebeans.runner('worker_id_1', '/path/to/config.yml');
			runner.go();</nowiki>
	===bin/beanworker===		===bin/beanworker===
	===Configuration file===		===Configuration file===

2014-05-11T15:37:16Z

Example

@@ Строка 316: / Строка 316: @@
 ===Example===
 ==FiveBeansRunner==
 ===bin/beanworker===
 ===Configuration file===

2014-05-11T15:36:24Z

Handlers

← Предыдущая версия		Версия от 18:36, 11 мая 2014
Строка 284:		Строка 284:

	===Handlers===		===Handlers===

			Handler modules must export a single function that returns an object. The object must have a field called 'type' with a brief descriptive string. It must also expose a function called work() with this signature:

			<code>work(jobdata, callback(action, delay))</code>

			*'''jobdata''': job payload
			*'''action''': 'success' \| 'release' \| 'bury' \| custom error message
			*'''delay''': seconds to delay if the job is released; otherwise unused

			If the action is "success", the job is deleted. If it is "release", the job is released with the specified delay. If it is "bury", the job is buried. All other actions are treated as errors & the job is buried in response.

			Here's a simple handler example.

			<code>module.exports = function()
			{
			function EmitKeysHandler()
			{
			this.type = 'emitkeys';
			}
			EmitKeysHandler.prototype.work = function(payload, callback)
			{
			var keys = Object.keys(payload);
			for (var i = 0; i < keys.length; i++)
			console.log(keys[i]);
			callback('success');
			}
			var handler = new EmitKeysHandler();
			return handler;
			};</code>
			The examples directory has another sample handler.

	===Example===		===Example===

2014-05-11T15:34:38Z

Jobs

← Предыдущая версия		Версия от 18:34, 11 мая 2014
Строка 279:		Строка 279:
	The job may also be a JSON array containing two items:		The job may also be a JSON array containing two items:

	[ tubename, jobdata ]		<code>[ tubename, jobdata ]</code>

	Where the second item is an object as specified above. This is for compatibility with the Stalker library, which wraps the job data this way.		Where the second item is an object as specified above. This is for compatibility with the Stalker library, which wraps the job data this way.

2014-05-11T15:34:10Z

Jobs

@@ Строка 269: / Строка 269: @@
 ===Jobs===
 ===Handlers===
 ===Example===

2014-05-11T15:33:27Z

Events

@@ Строка 224: / Строка 224: @@
 ===Events===
 ===Jobs===
 ===Handlers===

2014-05-11T15:28:01Z

constructor

@@ Строка 198: / Строка 198: @@
 *'''handlers''': hash with handler objects, with handler types as keys
 *'''ignoreDefault''': true if this worker should ignore the default tube timeout: timeout parameter used with on reserve_with_timeout, defaults to 10 (in seconds)
 ===Events===