[Cosmo-dev] Data reversion protection for servers

[Brian Moseley]

On 9/1/06, Jared Rhine <jared at wordzoo.com> wrote:

> + Effort to fix seems pretty small.  Cosmo UI doesn't have the "check ETag
> and version changes" problem that Chandler has.  It just would need to do "
> resource.version = resource.version + 1" right after it makes a change and
> before it writes that save back to the store.

as i mentioned in the other thread, we actually have a version
property on Items that hibernate uses to watch for concurrent changes.
if it's safe for us to set that property manually (eg when chandler
tells us a specific number), then this whole thing is trivial, because
changes through the cosmo itself (ui or protocol) will automatically
increment the version number.

> + I suggest I open a bugzilla enhancement, so this idea can be tracked and
> included in a much later release without needing to be tracked on any
> higher-level roadmap.

+1