[Pkg-javascript-commits] [node-async] 376/480: Clarify how cargo differs from queue
Jonas Smedegaard
js at moszumanska.debian.org
Fri May 2 08:58:43 UTC 2014
This is an automated email from the git hooks/post-receive script.
js pushed a commit to branch master
in repository node-async.
commit 4e2da57ce97d0fc5a12afa271f46efeb47a88830
Author: Dan Dascalescu <ddascalescu+github at gmail.com>
Date: Mon Feb 10 16:18:30 2014 -0800
Clarify how cargo differs from queue
This has confused some users - see issue #265
---
README.md | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/README.md b/README.md
index 951f76e..36b5b74 100644
--- a/README.md
+++ b/README.md
@@ -1004,6 +1004,10 @@ cargo will be processed altogether (up to the payload limit). If the
worker is in progress, the task is queued until it is available. Once
the worker has completed some tasks, each callback of those tasks is called.
+While [queue](#queue) passes only one task to one of a group of workers
+at a time, cargo passes an array of tasks to a single worker, repeating
+when the worker is finished.
+
__Arguments__
* worker(tasks, callback) - An asynchronous function for processing an array of
--
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-javascript/node-async.git
More information about the Pkg-javascript-commits
mailing list