Add partial backwards compatibility for delete with timeout 0

[GoogleCodeExporter]

We have accidentally had some backwards compatibility for deletion with a
timeout due to a bug (bug3) in the protocol parser that was fixed in 1.4.3.

Fixing this bug broke some clients that were always sending timeouts on
deletes.

We can add backwards compatibility specifically for a timeout value of 0,
but for values other than 0 (i.e. you actually desire a lingered delete),
the server will not perform as expected, so it will continue to tell you up
front.

This will be fixed in 1.4.4.

Original issue reported on code.google.com by dsalli...@gmail.com on 24 Nov 2009 at 10:15

[GoogleCodeExporter]

I've pushed up an issue_108 branch that tests a few scenarios and makes sure 
they
work.  Specifically, you will find the following behavior:

1. "delete key 0" works
2. "delete key 1" (for any non-zero value) still does not work and errors 
appropriately
3. "delete key 0 noreply" works (and doesn't reply)
4. "delete key 1 noreply" (for any non-zero value) still does not work, but no 
long
replies

Original comment by dsalli...@gmail.com on 24 Nov 2009 at 11:58

[GoogleCodeExporter]

This was fixed in 1.4.4.

Original comment by dsalli...@gmail.com on 27 Nov 2009 at 7:39

• Changed state: Fixed