>> make sense? aye it does, although I'm not sure what's at stake if we don't do as per your suggestion.
we also have an app-specific "kernel" in server dcope. should that be in every CFC as well? thanx barry.b From: David Ross Subject: RE: [CFCDev] using cfinclude within components (was Serializationof CFCs) Date: Fri, 09 Jul 2004 08:54:07 -0700 -------------------------------------------------------------------------------- > <cfset request.kernel.utils = server.kernel.utils> this doesn't copy anything, it just makes a reference to server.kernel.utils. > <cfreturn request.kernel.utils.arrayostructs(qry) /> this breaks encapsulation, as the CFC is now talking to a external scope. As mentioned , the best way to do this is to pass server.kernel.utils into your persistant CFC's constructor, assign into the variables scope (it's still just a reference), and then: > <cfreturn variables.utils.arrayostructs(qry) /> -- ___________________________________________________________ Sign-up for Ads Free at Mail.com http://promo.mail.com/adsfreejump.htm ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
