bomb when calling JSON.parse in redis-client callbacks

[fictorial]

bomb when calling JSON.parse in redis-client callbacks

[fictorial]

I am away from a usable computer ATM (on my iPhone) but I think you get back a Buffer object. Try calling toString on message .

[michaelsbradleyjr]

Thanks for the tip -- it works! I thought I had tried that very thing the other day, but perhaps I had mistakenly stuck the toString() function on the end of the wrong variable, i.e. it didn't seem to help.

Is there a "cheat sheet" or a easy way to remember which constructs will be synchronous and which won't be? I'm assuming here that calling toString() blocks the JSON.parse call until the buffer has been emptied into the stringified version of the message variable.

[fictorial]

Any operation that performs I/O is asynchronous. Any other operation is synchronous. Thus, calling toString on a Buffer is synchronous. However, it does nothing other than convert the bytes in the buffer to a String with the given encoding -- it does not "block" per se.

[michaelsbradleyjr]

Thanks, the insights are much appreciated, as is your redis-node-client library.

[fictorial]

I'm glad to help!

[michaelsbradleyjr]

By the way, this great piece of code has been performing well too. In some tests I've conducted I've been pushing ~20,000 requests per second, spread across four instances of your redis client (two per node.js process). Bandwidth has been upwards of 40+ Mbps. Very nice!! Thanks again, and please keep up the great work. ;-D

[fictorial]

Great! Stress-testing is something that I haven't done myself so this is great to hear.