Got lots of goodies on the ruby side, too. Need a day to double check I'm
not doing this same thing but would be good to go after that.
On May 24, 2010 3:22 AM, "Jeff Hammerbacher" <[EMAIL PROTECTED]> wrote:
I just pushed a fix to a not so nice bug in the Python client, where I was
not handling the CLIENT HandshakeMatch value correctly (rather than
processing the response, I was sending another RPC). For anyone using a
Python client, they're sending two RPCs any time the server has seen them
before but they have not seen the server before--pretty ugly, particularly
for non-idempotent server-side operations. I would love to get a release out
ASAP so folks can avoid this error. Worth it?