Bug 747 - Committing values should not necessarily remove all local objects and then reload them
Summary: Committing values should not necessarily remove all local objects and then re...
Status: RESOLVED DUPLICATE of bug 753
Alias: None
Product: Direct Objects
Classification: Unclassified
Component: Cache (show other bugs)
Version: unspecified
Hardware: PC Linux
: P1 major
Assignee: Werner Van Belle
URL:
Depends on:
Blocks:
 
Reported: 2011-01-14 15:16 CET by Werner Van Belle
Modified: 2011-02-13 14:13 CET (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Werner Van Belle 2011-01-14 15:16:58 CET
it might be ebtter instead, to simply keep most of the vlaues up to a certain amount of preloaded data and inform the server that we still have those values. How that will interact is not entirely clear, since in that case the server will need to know whether anything changed since the last use. It would also be a reliable idea to directly list which objects we still have from the last session whenwe start a transaction, isntead of laoding them all.
Comment 1 Werner Van Belle 2011-02-13 14:13:56 CET

*** This bug has been marked as a duplicate of bug 753 ***