Question about the factory pattern. From what I understand, the factory is useful when creating various implementations of various object families. However, when it comes to (my) web development, I find that I really only have one family of objects.
Now, don't get me wrong, even I have never going to have a different implementation of a factory, I like the idea of encapsulating object instantiation... but I just feel like it's a misuse. I know that SQL stuff might one day need a different implementation (gateways, DAO, etc) since I might switch (not really) to Oracle or Access or something. But take for instance, a singleton for Query Caching... if I use a factory to get that instance, is that wrong since I will probably never have to change that implementation? Or... am I just completely misunderstanding/misusing the use of factory pattern? ...................... Ben Nadel Web Developer Nylon Technology 6 West 14th Street New York, NY 10011 212.691.1134 212.691.3477 fax www.nylontechnology.com "Vote for Pedro" ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
