From 87e0997f2b184286dcdecca6f3432fb227060885 Mon Sep 17 00:00:00 2001 From: Chris West Date: Wed, 29 Jan 2020 14:28:42 +0000 Subject: [PATCH] docs: needle, not request --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index aa344bf..da299c9 100644 --- a/README.md +++ b/README.md @@ -8,10 +8,10 @@ We expect clients to eventually give up and just retry *without* the header, ski This implies your application should have other concurrency limiting or queuing in place, if appropriate. This might just be the node event loop. -There's a wrapper for `request-promise-native` available in `requestWorkerRuns`. This +There's a wrapper for `needle` available in `needleWorkerRuns`. This will attempt to locate a worker which isn't overloaded, and send the request to it. If the worker doesn't support this protocol, or a free worker cannot be found, -then the request will be run anyway; the same as if `request` was used directly. +then the request will be run anyway; the same as if `needle` was used directly. ## Example