On Fri, 18 Mar 2005 13:13:59 +0000, Alan Williamson <[EMAIL PROTECTED]> wrote: > Yes, I could cache them in SESSION/APPLICATION etc but thats overhead > and placing the responsibility on me, the CFML developer.
Right, because some CFCs can be cached in application scope and some can't. Some have to be created per-session or per-request. This is true of every OO language: it's why we see the Singleton design pattern, for example, to control how many instances of an object get created. > If somehow we could 'pool' object instances then this would reduce > memory/speed greatly. In some cases. > For the applications i am working on it would > increase the overall performance significantly. You are using stateless service CFCs rather than stateful object CFCs? If so, yes. > The majority of the > CFC's are not holding data per-se but operating on data passed in In your programs perhaps, not in mine. OO is about objects that have their own data and operate on it. Sure, not all objects have data but the promise and the power is about encapsulated data + behavior. -- Sean A Corfield -- http://www.corfield.org/ Team Fusebox -- http://www.fusebox.org/ Got Gmail? -- I have 50, yes 50, invites to give away! "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]
