Alex, I think in this case I need to. I have about 20 functions to execute,
each of which depends on the side-effects of the previous function. I can
basically make it synchronous by making what looks like a big 'V'
a(function(err) {
if(err) {
. . . . .
} else {
b(function(err) {
if(err) {
} else {
c(function(err) {
if(err) {
} else {
}
});
}
});
}
});
On Friday, April 18, 2014 11:34:41 AM UTC-5, Alex Kocharin wrote:
>
>
> 18.04.2014, 19:24, "Kevin Burton" <[email protected] <javascript:>>:
>
> I notice that simply leaving off the callback or making a callback null
> doesn't always make a node function synchronous. What is a good general
> pattern for making a node method synchronous (assuming the source for the
> method is available)?
>
>
>
> A usual advice about making a node method synchronous is "don't do that".
>
>
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
---
You received this message because you are subscribed to the Google Groups
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
