> That would do it. Would need to ensure we are memory-storing all that we > would need, as the RI update is based on object properties, datastream > properties, object->datastream relationships, RELS-EXT, RELS-INT, DC.
Ultimately, I think we need to have a complete reference to the object in the "before" state, and in the "after" state. I'm not entirely sure that needs to be in strictly in memory, though (i.e. existing managed datastreams can still point to the preserved content file, updated managed datastreams can point to where the new content is staged), but the end result is the same. If you recall from past HighLevelStorage proposals, the update method has looked something like: update(DigitalObject old, DigitalObject new); This is precisely so that plugin storage/index/cache modules can perform their own kind of diffing if necessary. I think if we can get closer to that mindset in fixing this bug, that would be a good thing. -Aaron ------------------------------------------------------------------------------ Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Fedora-commons-users mailing list Fedora-commons-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
