On 12/05/2010 17:36, Randy Watler wrote:
Scott, Bryan, Kris, and Ross:
I have been looking into existing Wookie persistent object
implementation and how I might maintain the existing Active Record
Pattern APIs. Thus far, it seems that there are basically two pluggable
approaches to choose from:
1. Maintain the existing Active Record Pattern/classes and use hidden
delegates for each object to support different persistence
implementations, or
2. replace the existing classes with interfaces and a persistence
component that encapsulates the implementations.
The advantage of keeping the Active Record Pattern intact is that it
maximally preserves the existing code base and designs, but in order to
make it pluggable it seems to require shadow objects and the complexity
that entails. Moving to a persistence component API with interfaces
allows more flexibility in which to deliver the persistence mappings,
but is obviously more intrusive.
Any implementation preference, thoughts, or comments?
For me ease of maintenance and clear APIs is always the way to go in the
long term.
A little short term disruption for long term gain is always worth it.
Ross
