Chris... I am trying to come up with a real world example of why a
flexible design that starts as singleton migrates to non-singleton.
How about a single mega print server that queues up all print jobs
and then routes each job to the next available printer. Normally
your production department has only one of theses babies so a
singleton design makes sense. But... by using the design pattern it
would be possible to switch to a pool of print servers without
recoding the caller. The caller just gets a print server. The caller
does not know if it is the only print server or one of many.
Regards,
Jeff
Quote:
>If you return multiple instances, is this really a Singleton
anymore?<
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!