Hi!
The code says " ", personally I call isgraph(). It would be nice to
see a standard definition.
For the binary protocol I think none of this should matter at all. A
key has a key length, so the question of valid characters should not
be relevant.
Cheers,
-Brian
On Dec 19, 2007, at 10:30 AM, Dustin Sallings wrote:
I just got a bug report for my client regarding multibyte
characters within a key. In order to fix it, I need to know what
*should* be allowed in a key.
The protocol document is fairly vague as far as what makes up a
key. It says some specific characters that *aren't* valid, but
seems to have been written with an ASCII mindset.
In the binary protocol, we have a lot of freedom, but that freedom
doesn't extend to the text protocol.
Should we constrain keys to ASCII, or force clients to understand
UTF-8 (or some other specific encoding)?
--
Dustin Sallings
--
_______________________________________________________
Brian "Krow" Aker, brian at tangent.org
Seattle, Washington
http://krow.net/ <-- Me
http://tangent.org/ <-- Software
http://exploitseattle.com/ <-- Fun
_______________________________________________________
You can't grep a dead tree.
