Thanks Scott, that thread was very helpful.
I think I get it now, but it does seem to me that executing the callback
synchronously in the particular ways I've been doing it is ok. If I were
following a convention like:
function connect(cb) {
process.nextTick(cb);
return {
foo: function() {
console.log('foo!');
}
};
}
function foo() {
var client = connect(function() {
client.foo();
});
}
foo();
.. then I totally see why we need to use nextTick there.
But I guess I'll change my public libraries to use nextTick() just in case
someone uses them in a strange way.
Thanks again,
Bryan
On Aug 21, 2013, at 5:33 AM, Scott González <[email protected]> wrote:
> https://groups.google.com/d/msg/nodejs/FNsM6Ns1MkE/4Ys-l1RI0Q0J
>
>
> On Wed, Aug 21, 2013 at 4:19 AM, Bryan Donovan <[email protected]> wrote:
> Thanks for the reply.
>
> However, this is the same answer as what I keep coming across that doesn't
> really answer my question. What is the downside? I want to see a real-world
> example of what happens when I don't follow this contract. I've yet to see an
> example of something bad happening in this situation. I'm sure I'm wrong,
> but I need to know *why*.
>
> When would someone ever call:
>
> getSomething(args, cb);
>
> ... and then assume they can call something else in the meantime?
>
>
> Thanks,
>
> Bryan
>
>
> On Aug 21, 2013, at 12:32 AM, Floby <[email protected]> wrote:
>
>> Same as above.
>> A "callback" is meant to be called back after some operations are made. In
>> node, that means they're probably gonna get called when the current stack
>> has unwound. If you called the callback synchronously, that means it behaves
>> differently.
>> process.nextTick un most cases execute the given function immediately after
>> the current stack ends (with some limitations for recursivity) so it's not
>> really a performance killer.
>>
>> Doing so helps you respect your function/method contract :)
>>
>> Saying that "in most case, it's not needed" is too big of an assumption of
>> what your user is doing with your code. IMO.
>>
>>
>> On Tuesday, 20 August 2013 19:47:22 UTC+2, Bryan Donovan wrote:
>> I have been writing node.js client code for a couple of years now, and have
>> authored a couple open source libraries, but somehow I missed the memo
>> telling me that I'm supposed to wrap 'synchrounous' callbacks in
>> process.nextTick(). I kind-of understand why that is a best-practice, but
>> what I don't understand is what the drawback is if you don't do it.
>>
>> For example, I write code like this all the time, and have never had a
>> single problem with it:
>>
>> function getSomething(args, cb) {
>> if (!args) { return cb(new Error('args required')); }
>> if (!args.id) { return cb(new Error('args.id required')); }
>>
>> SomeDatabase.get({id: args.id}, cb);
>> }
>>
>> What are the potential issues with not wrapping those arg checks in
>> process.nextTick()?
>>
>>
>> Thanks,
>>
>> Bryan
>>
>> --
>> --
>> 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 a topic in the
>> Google Groups "nodejs" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/nodejs/0TmVfX9z1R0/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> [email protected].
>>
>> For more options, visit https://groups.google.com/groups/opt_out.
>
>
> --
> --
> 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/groups/opt_out.
>
>
> --
> --
> 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 a topic in the Google
> Groups "nodejs" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/nodejs/0TmVfX9z1R0/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
> For more options, visit https://groups.google.com/groups/opt_out.
--
--
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/groups/opt_out.
