On Fri, Apr 21, 2006 at 06:58:03PM +0100, Dave Baker wrote:
> Okay, no problem. I'll fix the not-colliding-at-all issue. As for the header
> issue, I can fix that too by just comparing the first 72 bytes instead of the
> whole lot - is there any situation that needs the equals method to take this
Okay, no problem. I'll fix the not-colliding-at-all issue. As for the header
issue, I can fix that too by just comparing the first 72 bytes instead of the
whole lot - is there any situation that needs the equals method to take this
random part of the header into account? If not, I can just chang
On Thu, Apr 20, 2006 at 02:49:11AM +0100, Dave Baker wrote:
> Hi,
>
> So I've just spent a while tracking down why KSKs and SSKs don't collide,
> even
> if you insert different data. The answer is that in
> MultiPutCompletionCallback, onFailure gets called, but doesn't complete the
> request b
On Fri, Apr 21, 2006 at 06:58:03PM +0100, Dave Baker wrote:
> Okay, no problem. I'll fix the not-colliding-at-all issue. As for the header
> issue, I can fix that too by just comparing the first 72 bytes instead of the
> whole lot - is there any situation that needs the equals method to take this
Okay, no problem. I'll fix the not-colliding-at-all issue. As for the header
issue, I can fix that too by just comparing the first 72 bytes instead of the
whole lot - is there any situation that needs the equals method to take this
random part of the header into account? If not, I can just chang
On Thu, Apr 20, 2006 at 02:49:11AM +0100, Dave Baker wrote:
> Hi,
>
> So I've just spent a while tracking down why KSKs and SSKs don't collide,
> even
> if you insert different data. The answer is that in
> MultiPutCompletionCallback, onFailure gets called, but doesn't complete the
> request b
Hi,
So I've just spent a while tracking down why KSKs and SSKs don't collide, even
if you insert different data. The answer is that in
MultiPutCompletionCallback, onFailure gets called, but doesn't complete the
request because it's still waiting on some blocks. onSuccess then gets called
and s
Hi,
So I've just spent a while tracking down why KSKs and SSKs don't collide, even
if you insert different data. The answer is that in
MultiPutCompletionCallback, onFailure gets called, but doesn't complete the
request because it's still waiting on some blocks. onSuccess then gets called
and s
