Re: [Subclipse-users] 0.9.106: File lost after update

Aaron Digulla wrote:

> - Outgoing change: When a user does a commit of some files during a sync
> run (ie. you have now incoming changes, new revisions due to the commit
> and changed working copies which will are not revisions, yet), then
> update the highest known revision number after the commit.

Open issue here: Imagine two users A and B. File X in the repo is newer
than their working copies.

A runs synchronize
B runs synchronize
A commits file X
B updates file X

What will B expect to get?

Worse:

A runs synchronize
B runs synchronize
A commits file X
B updates file X
B changes file X
B commits file X
A updates dir of file X

(note: both users run sync just *once*).

Will A expect the file to change?

Maybe the only solution is to go back to individual updates but to group
them by revision numbers:

- Remember the highest revision number during population the sync view.
- For all files which are committed individually, remember the highest
rev for them. Don't touch the revs for the other (incoming) files.
- For all incoming changes, update to the number we got during the
population step. This includes directories but not the files in them
(non-recursive update).

Another solution: During sync, request an actual update but don't apply
it, yet. Apply the parts of the update individually when the user
requests it.

Regards,

-- 
Aaron "Optimizer" Digulla a.k.a. Philmann Dark
"It's not the universe that's limited, it's our imagination.
Follow me and I'll show you something beyond the limits."
http://www.philmann-dark.de/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org