> Just in case you do not know (like most people) there is > exactly ONE system on the market that makes transparent > persistence, and this is in the java world. This is done by
There is another style of persistance which is to persist the object via some sort of serialisation and then record any changes in a log, and then taking full snapshots of the system every now and then. This is the basis of the prevayler concept. Having played with it a little it's quite neat and robust. The .net prevayler it is quite _transluscent_ with the only requirement being a container that inherits from MarshalByRefObject, the objects being [Serializable] along with some startup glue code to get the persistence engine up and running (which is about 3 lines). http://bbooprevalence.sourceforge.net With object persistence most people seem to think only of database persistence (and for good reason!! ACID being four of them) and, like other people have pointed out, that the backing store is a database has an impact on the object model. Maybe using an object prevayler will allow for more natural object designs. Chris =================================== This list is hosted by DevelopMentorŪ http://www.develop.com Some .NET courses you may be interested in: NEW! Guerrilla ASP.NET, 17 May 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls View archives and manage your subscription(s) at http://discuss.develop.com
