[Cosmo-dev] Bug Roundup

[Brian Moseley]

On 10/3/06, Randy Letness <randy at osafoundation.org> wrote:

> Right, but there isn't an easy way to tell if there is another request
> operating on the same
> resource.  We could do some in-memory implementation for now, but if we
> want to
> support multiple cosmo servers talking to the same db, the
> implementation would be
> more complex.  We are going to need this for locking, though.

is there a reason we can't assume that a stale object exception ==
concurrent modification by another request? even in the case of
multiple cosmo instances, hibernate in instance B will notice that the
version number in the database has suddenly advanced when it goes to
save request B.