-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feature request - async.minimum #899
Comments
Take a look at |
I think they mean something more like |
Closing this in favor of #568 . I'll add |
I think "first" is actually better than "minimum". The only problem with "first", is that the result I want is not just the first result, it is the first result that has a defined value for the second callback parameter, the first being a potential error, as in error first callback. This is something that could be easily generified for popular use. |
Yeah, "first" is not without its problems. I think coming up with a good name is most of the work remaining for that feature. "Cache invalidation and naming things" as the saying goes. |
http://www.thesaurus.com/browse/pristine async.pristine haha, pristine seems to mean both earliest and immaculate |
I am looking for the functionality described here:
http://stackoverflow.com/questions/32323611/node-js-async-but-with-minimum-priority
the question is:
What is the best way to create parallel asynchronous HTTP requests and take the first result that comes back positive?
//something like this, where one call goes to some API and a parallel call goes to our Redis store to see if we already have the value:
The text was updated successfully, but these errors were encountered: