I have a design question regarding managing new, modified, and delete objects. Our application is session based where the users can do multiple things and then save the changes. The problem we are facing is managing the new, modified, or delete objects. When the user clicks 'Save' we need to determine which objects need to store to the database and which objects need to be deleted. My question is how have other groups handled this situation? The current idea we are discussing inhouse is to create a managing object that is aware of all fetched objects. The fetched objects notifies this manager when changes (i.e. set method) occur or a delete method is called. Then when the user clicks save we request from the manager which object are modified, new, delete. We have not spent much time refining the idea and before we do I would like to know how other developers have handle this situation and any other thoughts on this.
Thanks John
