pattern. If your objects are volitile enough to require a factory, the
thing producing them has to be at least as volitile. Thus you almost have
to use a factory to get the factory, though it's probably best implemented
as a static method on the parent abstract factory.
> -----Original Message-----
> From: Kwang Suh [mailto:[EMAIL PROTECTED]
> Sent: Thursday, February 26, 2004 12:48 PM
> To: CF-Talk
> Subject: Re: RE: What is a Factory?
>
> Factories exist so that the developer doesn't need to worry
> about what object they're creating (doing Foo foo = new Foo()
> is considered very bad practice by some members of the OO
> community). This way, one can change the factory to produce
> different objects within an object hierarchy.
>
> Take a look here:
> http://www.dofactory.com/Patterns/PatternFactory.aspx
>
> Personally, this is one of the more useful design patterns
> out there, but I've seen it misused (I once saw a system that
> used a factory object to create... factory objects).
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
