on 1/26/00 2:19 PM, Kimbro Staken <[EMAIL PROTECTED]> wrote:
> How does this service design work with services that are implemented as a
> singleton? Would you treat the actual service implementation as a proxy
> object which can maintain state and then hands the request to the singleton
> service when execute is called?
A service is not a singleton. The TurbineServiceManager is. It will return a
cached "Service" object. That is the point of this whole services
stuff...instead of creating a whole bunch of singleton's, you only have one
singleton that brokers out new instances of objects. those instances are
cached so that new isn't called each time on those objects and effectively
gives you the same thing that a singleton will give you.
-jon
--
Come to the first official Apache Software Foundation
Conference! <http://ApacheCon.Com/>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
