Like it was mentioned, there isn't a way to get rid of callbacks because that's what gets us evented io in the first place.
So at the end of the day, it's how you want to handle async code. My preference is the lightest possible abstraction written by @substack https://github.com/substack/node-seq. No fibers, thread-like things or any other crazyness, it just runs stuff sequentially. An yeah writing blocking code is a Bad Thing™ in node. On Sunday, March 18, 2012 8:23:37 PM UTC-4, Angelo Chen wrote: > > Hi, > > got this : > > function get_next_id() { > rclient.incr("next_id", function(err, reply) { > return reply > }); > } > > will call this with: > > var next_id = get_next_id() > > this won't work, because function returns even before 'reply' was > taken from rclient( a redis), one solution is, passing a call back to > the function, is there any other way? thanks. > > Angelo > -- 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
