>Any reason why you wouldn't want to use something like ColdSpring? I've got a few ... even tho' ColdSpring seems very cool indeed.
1) it requires a mapping 2) combined with the fact that it's not a 1.0 release yet, which means the API is still very much open to change, as i understand it. One of the big advantages for me about using a Factory.cfc like i've outlined as a single interface for creating object instances is that i can: ... Place it in a /model subdirectory with the rest of my components ... Instantiate it from Application.cfm/cfc as a singleton using the notation createObject(model.Factory) ... And let Factory create the rest of my cfc instances _without_ needing a mapping! What that allows me to do is set up a server and drop in many instances of the same application without needing to modify the code in each one to accomodate different mappings for each separate installation, and free to make variations in each application according to our clients' varied and unpredicable requests for customization without concern that i'd break another app doing so (if we went with a shared model directory for all instances on a server). The core benefit here is that it allows us to let our business expand - even quickly - without fear that we'll drown under 100's or 1000's of different installations to install and maintain. I know this doesn't present a problem in other situations. But in this case, each installation would become very dependent on ColdSpring, and i'd like to move toward each installation being, as much as possible, self sufficient so the code is portable and easily installable, even next to other installations of the same app. And even if i need to place an installation on a shared server somewhere for a particular client. I don't even want to think about the possibility anymore that a mapping will be already taken. That's not to say i might not be comfortable using it down the line and adapting our codebase to suit. But i'm not there yet. Even so, i think ColdSpring is "auwsum". (Did i say that correctly?) :) nando >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] >Behalf Of Sean Corfield >Sent: Thursday, November 03, 2005 11:29 PM >To: [email protected] >Subject: Re: [CFCDev] Factory Pattern > > >On 11/1/05, Scratch <[EMAIL PROTECTED]> wrote: >> I was recommended to build a Factory object to create my CFCs in the >> following manner: > ><big snipperoo> > >Fascinating thread with lots of interesting ideas being bounced around. > >Very surprised no one suggested using ColdSpring to manage all of the >object creation, initialization and dependency resolution... I suspect >it would handle everything you're trying to do in a much cleaner >manner (and cleaner than most all of the suggestions from other folks >in this thread). > >Any reason why you wouldn't want to use something like ColdSpring? >-- >Sean A Corfield -- http://corfield.org/ >Got frameworks? > >"If you're not annoying somebody, you're not really alive." >-- Margaret Atwood > > >---------------------------------------------------------- >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]
