Lazy commit strategy.

[Sebastian Sastre]

> -----Mensaje original-----
> De: magma-bounces at lists.squeakfoundation.org 
> [mailto:magma-bounces at lists.squeakfoundation.org] En nombre 
> de Chris Muller
> Enviado el: Lunes, 29 de Octubre de 2007 22:04
> Para: Keith Hodges
> CC: magma at lists.squeakfoundation.org
> Asunto: Re: Lazy commit strategy.
...
> 
> "User does a whole bunch of work on the model"
> ...
> 
> "User is ready to commit, merge everyone elses changes into his own"
> mySession begin.
> 
> "user reviews integrated model, makes any additional updates"
> ...
> 
> "Done reviewing, everything looks good."
> mySession commit.
> 
>  - Chris
> 

Hi Chris,

	I think I don't get something on this scenario. 

	Magma will show fresh versions of the objects after the begin? By
fresh I mean commited changes of other users made just before the begin of
the merger user that was doing it's "bunch of work". 
	If so there could be changes made by others than the merger.
	How the merger will be guaranteed to see a fresh state of the model?

	cheers,

Sebastian
PS: I'm asuming that you have on those sessions
refreshObjectsEvenIfOnlyChangedByMe in false