[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Newsgroup Home]
[news.eclipse.tools.emf] Re: [CDO] Passive updates
A session that Passive update is set to false do no received others changes until you ask for it.



Anders Forsell wrote: 
I am not sure I fully understand the concept of passive updates.

If a client starts modifying a CDO resource I understand that the objects are loaded on demand as they are needed. If another client modifies the same resource and commits a transaction will the client receive updates to its cached objects? 
[SIMON] Only if passive update on session1 is true.

Are these modifications done on a 
separate thread and how are conflicting changes handled?

[SIMON] Separate threads (In the case where passive update = true

When not using passive updates what happens during a session refresh?
[SIMON] All objects in the caches are updated
(especially when there are modifications that have not been committed yet).
[SIMON] In this case two things could happen
1- The client modified objectA and server didn't it. Nothing special.
2- The client modified objectA and the server have another version of it. (basically someone else modified and committed that object). In this case the state of that object will be turned at CONFLICT. You will have a problem to commit now since you cannot commit until you rollback or resolve these conflicts.



Simon



Thanks,

---
Anders


Eike Stepper wrote:
Simon McDuff schrieb:
Anders Forsell wrote: 
I have turned off passive updates for my CDO session. Do I need to
refresh the session when committing a transaction, or is it done
implicitly?

---
Anders

At the moment, yes.

But I think it will make sense to refresh automatically. WHat do you
think ?

Hmm, not sure about this one:
Refreshing the session affects *all* views/transactions of that session.
Is that something that should be implicitely done by one of the
transactions?

Cheers
/Eike

----
http://thegordian.blogspot.com