Boy that seems like a useless abstraction... The factory that is ...
the Manager I understand, but it seems like if you wanted a new
something to put into a manager, you'd just use "newThing = new
Something(blah,blah)" instead of having a separate "factory" object to
create them. Is there some other reason for it that I'm not aware of?

> On Thu, 2004-02-26 at 11:17, Troy Simpson wrote:
>> All,
>>
>> I noticed that some application user the terms Factory
>> and Manager in
>> the Class/Object Names.  Like AppFactory, AppManager, and
>> EventManager
>> in Mach-II
>>
>> 1. What is the general definition of a Factory?
>> 2. What is the general definition of a Manager?

> In a very basic way (from a java stand point) a factory
> produces and a manager manages

> so you'd tend to see stuff like

> Thing thing = Factory.createInstance() not
> Manager.createInstance()

> Manager.add(thing)
> not Factory.add(thing)

> Pretty much just what you think it does :)

> --
> Rob <[EMAIL PROTECTED]>

>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to