> I've been working on this very thing for a few days. I'm > starting with > > *** Not enough time :-)
Tell me about that! > 2. Non-invasive to client classes. You don't have to derive > from some > PersistentObject or implement special interfaces. Basically a > reflection > approach with help from custom attributes. > > *** BZZZZ - wrong. You ARE invasive if you ask for custom attributes. > You will never be able to serialize private attributes "non-invasive". Perhaps I should say - not - "too" invasive. I think there is some yin-yang wrt ease of use and the ability to persist everything about a object. > 3. Fast and scalable > > *** I object - NOT with reflection. Oh - sure play the "Reflection is slow" card. You take a hit the first time the metadata is accessed but afterwards I've found its very adequate. Given the usage patter than a typical application will save and load a very finite set of class types the reflection performance problem isn't one. > 4. Database neutral implementation > > *** Ok. OK!? This is the winning feature IMHO! :) > *** It might. I have an O/R mapper here ready for about half > a year - it > was supposed to become a product but will probably never. We seriously > think of making it open source :-) Perhaps when you if there is enough interest (and I'm further along) we could get something going here. Jim You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
