Created
May 8, 2010 19:46
-
-
Save juvenn/394735 to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
node> redis.set("greeting", "Thank you, Brain, for building us redis-node-client") | |
node> redis.get("greeting", function(err, reply) { sys.puts(reply); }) | |
node> Thank you, Brain, for building us redis-node-client | |
redis.get("greeting", function(err, reply) { sys.puts(typeof(reply)); }) | |
node> object // oops, it's an object instead of string | |
redis.get("greeting", function(err, reply) { sys.puts(sys.inspect(reply)); }) | |
// What's this? a buffer representation? | |
node> { '0': 84, '1': 104, '2': 97, '3': 110 ... , length: 51 } |
Buffer, for binary compatibility.
I see, thanks for confirming!
node.js api has documented buffer.toString(), my ignorance:
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What kind of object is the
reply
? It must have antoString
method, sosys.puts
could print the string; but why==
comparison will be true, but===
will be false? I'd expect==
comparison will be false as well. And the inspected result seems it's ASCII encoded.So we should first hard convert the reply to string, before we handle this string, right?
Thanks!