When you expose your shared fuses via fuseactions this way, how do you prevent that these fuseactions are called directly by a browser? Or, more general: how do you tell a browser from yourself when a fuseaction is called?
Regards, Wouter. -----Original Message----- From: Nat Papovich [mailto:[EMAIL PROTECTED]] Sent: 21 March 2002 21:33 To: [EMAIL PROTECTED] Subject: RE: FB3 and common directories? Alan, If you adopt a quasi-MVC approach, you can still use your "common" folder idea, but make it its own circuit. Then, any circuit can request any fuseaction in that circuit. The common circuit returns data in the caller scope, since it is only shared via <cfmodule>. So if you had a query fuse that you found was being used all over the place, you could make it a separate fuseaction in the "common" circuit. Then, any circuit's fuseaction that would normally look like this: <cfinclude template="../../shared/queries/qry_greatQuery.cfm"> would instead look like this: <cfmodule template="index.cfm" fuseaction="shared.greatQuery" return="localResult"> Now, directory pathing is out of the way, and the communication between the 2 circuits is very clean. What exactly goes in inside the shared.greatQuery fuseaction is not of concern to the calling circuit. It just knows that it will get something in the localResult variable. NAT ==^================================================================ This email was sent to: [email protected] EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^================================================================
