Re:Wait.for: Sequential programming for Node.js (beta)
by tg3 on Friday August 23, 2013 @03:08AM
(#6262134)
in your example below, you do have to wrap it in a call to `Fiber()`, although you've disguised it as `launchFiber`, which you pass `handleRequest` to (I would call that wrapping `handleRequest`.
That is probably a worthwhile tradeoff, but the first time I read through it, that mechanic wasn't obvious to me.
Re:Wait.for: Sequential programming for Node.js (beta)
by lucio on Friday August 23, 2013 @04:05AM
(#6262296)
It's not 'disguised', it's abstracted.
launchFiber does what it's name implies: launchs a fiber.
How it is achieved 'internally', it's irrelevant as long the abstraction is not leaky.
Today launchFiber is calling the fn inside a Fiber(), tomorrow could be launching the fiber by means of a generator.
The idea was to create a very simple abstraction to avoid callback hell, adding low or no complexity, and keeping the flexibility to use all the existing async fns with a callback or just "wait" for the results.
You don't have to wrap all your code in a call to `Fiber()`
full classic node-server sample: