Hello everyone, i took some time on the weekend to dive into the identity map implementation of the upcoming ezc release. I have to say its an awesome solution given the technical difficulties that the current implementation of relations puts on an identity map. Thumbs up Toby :-)
What I like is that it not only knowns about the identity of an object, but also about its references to other objects. This way from what i can tell (and tested) it keeps the object state completly consistent to that in the database. A minor detail that i didn't like so much is the code-duplication of identity map decorator and the load handler, which is difficult to eliminate due to both of them being "far away" in the package structure. But considering that the 3 handlers have only been created to simplify the persistent object manager they still belong together somehow. Maybe it is time to abstract'ize the loader (possible the save and delete handler too) and make the identity map decorator have one implementation also that removes code duplication. Abstract handlers have the advantage that they help in the further development of PO with new features. greetings, Benjamin -- Benjamin Eberlei http://www.beberlei.de -- Components mailing list Components@lists.ez.no http://lists.ez.no/mailman/listinfo/components
