CJ-
Thanks for the reply.
I was referring to persisting data in the database. It doesn't seem like
the factory should be doing this, but I could be wrong. Currently, I use
the base object's (named ObjectInfo) Save method to persist information. I
have a blob field that contains a serialized collection of properties for
its decendant's properties
Here's what I want to do:
* Build a factory that will create a new ObjectInfo instance or an
instance of one of its decendants.
* The factory will return a collection of ObjectInfos that match given
criteria and the security clearance of the user.
Thoughts?
Craig
"CJ Taylor" <no****@blowgoats.com> wrote in message
news:10*************@corp.supernews.com...
Can you give me an example of what you mean by persisting data when its
changed? As in notifying the underlying data storage? Or other objects
within the program that need to know when data is changed?
-CJ
"Craig Buchanan" <so*****@microsoft.com> wrote in message
news:uO****************@TK2MSFTNGP09.phx.gbl... I've seen design patterns for class factories that work well to create
(fetch) objects, but I haven't seen anything about how to persist the
class' data when it has changed. Is this done thru the factory? What about
security? I'm assuming that the factory should enforce security.
Has anyone seen examples of this?
Thanks,
Craig Buchanan