> There were strong arguments for keeping keys compatible with both ASCII and > binary clients, to the point where it was decided to keep > parity between the two. > > We can certainly revisit that now, but I don't remember anyone advocating > for arbitrary bytes in keys other than asking if we should and > having someone else say we should keep the same constraints on both sides. > (that's from memory, I don't remember who said what, but it made > sense at the time) > > The client side checking predates the protocol implementations anyway. We > can pull it from the clients and just wait for the server to > send it back, but there are cases where it'll cause a lot of confusion in the > ascii protocol at least since your key can otherwise look like > a complete request.
Just... add a flag so it can be turned off? It's a sane default, but hurtful if you ever need blob keys. None of the original clients checked keys, and that sucked.
