> Calm down. It clearly wasn't 50% of the use cases given that it's just > now come up. :)
It was part of the whole damn point of implementing the protocol. We wanted three things: binary keys, proper quiet commands, and CAS on everything. The rest is exactly the fucking same in ASCII. I reserve the right to be annoyed. So I guess that's 33.3% of the point... It's also how we advertise and document the damn thing. > I'm not absolutely sure, but I do remember something about removing it > and discussing it with Dustin at some point. I doubt if either of us > remember the conversation exactly. Maybe Dustin will pop up and call me > a liar. I doubt that though. > > I'd surely take a patch/issue to add a configuration flag to ignore this > check, but there's not one currently. > > In my personal opinion, I think we should allow binary keys. It is > useful. I hope someone does send in a patch.
