Nice. Might just try this out in my next project.
I've actually built something similar back when I was doing C# but were not
able to finish due a stupid compiler bug.
It basically is a function(req, resp) { } thing, but which was made a first
class thing in my framework and methods
were
On Apr 17, 2013, at 2:42 AM, chakrit konsh...@chakrit.net wrote:
One big glaring caveat with pipeworks though:
Callback (the next() function in this case) should always accepts error as
first argument.
Otherwise you will break a lot of established pattern and convention with
callback
Anticipating the usual why not use the async module? question, I posted a
pipeworks vs. async comparison here:
https://gist.github.com/kevinswiber/5394922
The Premise:
1. Start a pipeline.
2. Delegate to workers passed into the execution context.
3. Pause until the workers are done.
4. Continue
