summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGregor MacLennan <gmaclennan@digital-democracy.org>2015-03-29 19:41:40 -0700
committerGregor MacLennan <gmaclennan@digital-democracy.org>2015-03-29 19:41:40 -0700
commite7ab7d73d1e81a6965343db09f1e297af9360811 (patch)
tree48a5008beb5e7d66a22a005d6fc90188760c02f8
parent996ff7fcff6a34ba94d09cbd8a1a6ea3e6d36481 (diff)
downloadasync-e7ab7d73d1e81a6965343db09f1e297af9360811.tar.gz
Add cargo animation to README
For some reason the README only included one of @rhyzx 's brilliant animations, which really help explain `cargo`
-rw-r--r--README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.md b/README.md
index 6cfb922..88ecd73 100644
--- a/README.md
+++ b/README.md
@@ -1154,7 +1154,7 @@ Creates a `cargo` object with the specified payload. Tasks added to the
cargo will be processed altogether (up to the `payload` limit). If the
`worker` is in progress, the task is queued until it becomes available. Once
the `worker` has completed some tasks, each callback of those tasks is called.
-Check out [this animation](https://camo.githubusercontent.com/6bbd36f4cf5b35a0f11a96dcd2e97711ffc2fb37/68747470733a2f2f662e636c6f75642e6769746875622e636f6d2f6173736574732f313637363837312f36383130382f62626330636662302d356632392d313165322d393734662d3333393763363464633835382e676966) for how `cargo` and `queue` work.
+Check out [these](https://camo.githubusercontent.com/6bbd36f4cf5b35a0f11a96dcd2e97711ffc2fb37/68747470733a2f2f662e636c6f75642e6769746875622e636f6d2f6173736574732f313637363837312f36383130382f62626330636662302d356632392d313165322d393734662d3333393763363464633835382e676966) [animations](https://camo.githubusercontent.com/f4810e00e1c5f5f8addbe3e9f49064fd5d102699/68747470733a2f2f662e636c6f75642e6769746875622e636f6d2f6173736574732f313637363837312f36383130312f38346339323036362d356632392d313165322d383134662d3964336430323431336266642e676966) for how `cargo` and `queue` work.
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