* Greg McCarroll ([EMAIL PROTECTED]) [011104 11:52]: > ... > Imagine a persistent object that we only want to save when its > destroyed/commited and to do so we need to mark it as `dirty' > i.e. changed since it was loaded (There are also some interesting > bits connected to transactions with this scenario, but I digress). > > Now if we want we can either ... > ... > Tie it and automatically mark it as dirty if some does a set. > > Now I've been playing with my own secret P5EE compliant[1] persistence > ``engine'' (whatever the hell that means) and I like the 4th option > with the tie in turn calling the get/set method to do so in the store > section and a dirty bit being set because of it.
FWIW, this is what SPOPS does. Seems to work pretty well, and once you've made the leap to use tie you've opened up lots of interesting state maintenance ideas. Chris -- Chris Winters ([EMAIL PROTECTED]) Building enterprise-capable snack solutions since 1988.
