I don't think that is what he is asking Ben. He is not talking about
making the CFC depend on request vars, rather, he is talking about
putting an instance of a CFC in the request scope. So he can do crap
like this:
application.cfm:
<cfset request.logger = createObject("component","myKickButtLoggerCFC")>
foo.cfm:
<cfset request.logger.log("critical","App has broken")>
sometag.cfm:
<cfscript>
stuff;
stuff;
more stuff;
request.logger.log("info","Added user bob");
</cfscript>
=======================================================================
Raymond Camden, ColdFusion Jedi Master for Macromedia
Email : [EMAIL PROTECTED]
Yahoo IM : morpheus
"My ally is the Force, and a powerful ally it is." - Yoda
> -----Original Message-----
> From: Ben Johnson [mailto:[EMAIL PROTECTED]]
> Sent: Friday, June 07, 2002 10:44 AM
> To: CF-Talk
> Subject: RE: Opinion: CFC / Request scope question.
>
>
> > However, I'd still like to know peoples
> > thoughts on pushing a component into the request scope.
>
> I have not worked *too* much with CFCs, with the exception of
> with Flash
> Remoting, but the idea of putting the CFCs in the request
> scope seems to be
> a bit anti-OO to me. I have always thought that you should
> pass references
> or values to the CFC you are calling. It doesn't seem very
> scalable to make
> a CFC assume something is already created in the request
> scope or even that
> the variable that is created is specifically named a certain way.
>
>
>
> Ben Johnson
> Hostworks, Inc.
>
>
______________________________________________________________________
This list and all House of Fusion resources hosted by CFHosting.com. The place for
dependable ColdFusion Hosting.
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
