Hi Patrick,
On Mar 9, 2012, at 14:30 , Patrick Ohly wrote:
> On Tue, 2012-03-06 at 14:50 +0100, Patrick Ohly wrote:
>> I haven't look into this yet, but still have it on my radar.
>
> Done in the meego.gitorious.org master branch. I found that checking for
> collisions is hard (not all records a
On Tue, 2012-03-06 at 14:50 +0100, Patrick Ohly wrote:
> I haven't look into this yet, but still have it on my radar.
Done in the meego.gitorious.org master branch. I found that checking for
collisions is hard (not all records are in memory), so I settled for
making the chance of collisions smalle
On Thu, 2012-02-16 at 18:14 +0100, Lukas Zeller wrote:
> On Feb 13, 2012, at 14:35 , Patrick Ohly wrote:
>
> > Instead of repeating myself, let me quote the commit messages of the
> > relevant commits on that branch below. There are a few more commits in
> > that branch. Lukas, what do you think?
Hi Patrick,
On Feb 13, 2012, at 14:35 , Patrick Ohly wrote:
> Instead of repeating myself, let me quote the commit messages of the
> relevant commits on that branch below. There are a few more commits in
> that branch. Lukas, what do you think?
Thanks for these patches (the one with firstReadNe
On Tue, 2012-02-07 at 16:05 +0100, Patrick Ohly wrote:
> On Mon, 2012-02-06 at 21:29 +0100, Patrick Ohly wrote:
> > I'm currently experimenting with a different approach for handling the
> > 409 in the binfile client: when an Add fails with 409, catch it as it is
> > done at the moment, but then te
On Mon, 2012-02-06 at 21:29 +0100, Patrick Ohly wrote:
> I'm currently experimenting with a different approach for handling the
> 409 in the binfile client: when an Add fails with 409, catch it as it is
> done at the moment, but then tell the server that it was mapped to a
> dummy LUID. Mark that L
