Surely you meant a DAOFactoryFacadeFactoryRegistry, right? You want to keep things as abstracted as possible. ;)
I've oft wondered if people would be able to tell the difference between legit design pattern applications and totally spurrious extensions on the theme. Obviously the Factory Facade Factory Registry Pattern is rather a foolish one, but how do you make that distinction, ya know? Kind of an interesting problem, and one without a definite solution, but you have to make exactly that distinction many times throughout the course of designing even a single, fairly simple, application. I suppose thats why it takes a human to write code though, rather than just letting the machine do it for you. cheers, barneyb On 11/15/05, Patrick McElhaney <[EMAIL PROTECTED]> wrote: > On 11/15/05, Barney Boisvert <[EMAIL PROTECTED]> wrote: > > That'd be a registry, probably named DAORegistry in this case. But > > assuming the registry is part of a single app, I'd definitely take the > > time to wrap it up in a factory facade, because to the rest of the > > app, that's what it is. > > > > Well, I would probably take your factory facade and hide it behind a > DAOFactoryFacadeService. ;-) > > Patrick > -- Barney Boisvert [EMAIL PROTECTED] 360.319.6145 http://www.barneyb.com/ Got Gmail? I have 100 invites. ---------------------------------------------------------- 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]
