I think I misrepresented the idea. The thought was that you would have a single manager collection that would manage all of your managers. This manager collection would always exist and would return instances of other managers upon request.
This manager would be your single access point. It could manager your manager instances destroying those that have been used in a while and cut down on the manager bloat. The Managers component would only be responsible for managing managers, not singletons themselves. Jim Davis > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf > Of Matt Liotta > Sent: Monday, September 06, 2004 9:38 PM > To: [EMAIL PROTECTED] > Subject: RE: [CFCDev] singleton pattern > > > So I take it that the idea of using a single Managers component to > access > > all of your managers wouldn't fly? > > > How would you have a single manager component if you need an instance of a > manager component to manage singletons? > > -Matt > > ---------------------------------------------------------- > You are subscribed to cfcdev. To unsubscribe, send an email > to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' > in the message of the email. > > CFCDev is run by CFCZone (www.cfczone.org) and supported > by Mindtool, Corporation (www.mindtool.com). > > An archive of the CFCDev list is available at www.mail- > archive.com/[EMAIL PROTECTED] ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
