What's with the load() method? Well, load() gives you one public interface to code to. The implementation details within Factory can change without affecting the rest of your app.
Do you see a drawback to that? Maybe there is one ... my working hypothesis at the moment is that it would be better in the long run to stay with a single interface and work out any drawbacks in another way. >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] >Behalf Of Patrick McElhaney >Sent: Wednesday, November 02, 2005 6:51 PM >To: [email protected] >Subject: Re: [CFCDev] Factory Pattern > > >What's with the load() method? > >Why don't you just make the createObjectXXX() methods public and call >them directly? > >Patrick > > >-- >Patrick McElhaney >704.560.9117 >http://pmcelhaney.weblogs.us > > >---------------------------------------------------------- >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] > > ---------------------------------------------------------- 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]
