Neil Schemenauer wrote:
>>With Durus, how would you handle an application which has frequent
>>concurrent writes to the same object?  Example transactions would
>>include adding an item to a dictionary, or incrementing a value.
>
>
> First, we try to avoid designs that require that.  Second, our
> transactions are short (i.e. we call abort() right before
> calculating something and commit() right after).  Third, our write
> rate is low.

This didn't really answer my question.  Some applications cannot
completely eliminate data contention.  Likewise, they might require more
complex transactions that alter the state of several objects.  And yes,
the write rate for your application happens to be low-- but I was trying
to get an idea if Durus was suitable for applications with more
demanding characteristics.

Regards,
-John


--
http://giftfile.org/  ::  giftfile project