No particular reason. I almost always just use "self" (being very lazy) but
sometimes I need request.self.

Hal Helms
Team Allaire
[ See www.halhelms.com <http://www.halhelms.com>  for info on training
classes ]


-----Original Message-----
From: Ryan Wood [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 13, 2001 10:01 AM
To: Fusebox
Subject: RE: XFB questions


Hal-

In the example below, what is the reason for defining both "self" and
"request.self"? Why would you need two, rather than always using
"request.self"?

Ryan


-----Original Message-----
From: Hal Helms [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 13, 2001 9:15 AM
To: Fusebox
Subject: RE: XFB questions


Answers:

1. Just a preference; I think moving it to myGlobals would be fine--and
probably less confusing for people initially.

2. I've cleaned this up. Here's a recent myGlobals from an app I'm doing for
a book on CF:
<cfif NOT IsDefined( 'application.applicationName' )>
 <cfapplication
  name="Search"
  clientmanagement="Yes"
  setclientcookies="Yes"
  sessionmanagement="Yes"
  sessiontimeout="#CreateTimeSpan( 0, 0, 30, 0 )#">
</cfif>

<cf_Nesting>

<cfif NOT IsDefined( 'request.Circuits' )>
 <cf_formURL2attributes>
 <cfinclude template="Circuits.cfm">
</cfif>

<cfparam name="self" default="index.cfm">
<cfparam name="request.self" default="index.cfm">

Now, we only do the initialization if needed. Good points, Erik.

Hal Helms
Team Allaire
[ See www.halhelms.com <http://www.halhelms.com>  for info on training
classes ]


-----Original Message-----
From: Erik Voldengen [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 13, 2001 8:57 AM
To: Fusebox
Subject: XFB questions


I've been playing around with my own version of XFB, and I'm finally
trying to conform to what seems to be the norm out there so I'm ready
for the next round of craziness.

So I've got a couple style questions for the masters of XFB.

1) I don't understand why some of the stuff that clutters up index.cfm
   isn't placed in MyGlobals.cfm (e.g. call to formurl2attributes,
   circuits.cfm, cf_nesting, and cfparam of attributes.fuseaction).  Is
   this just a matter of preference, or is there some important reason
   for this?

2) I take it you want to make MyGlobals/Index.cfm include everything it
   needs to either stand up as a home application, or as a circuit within
   one.  So it seems like a lot of routine and initialization code (ie the
   elements listed above) are run multiple times for non-home applications.
   Why do we do this?  Simply for the simplicity of reusing circuit apps?
   Or is there a bigger reason?  I don't see how this is better than the
   old app_globals/app_locals scheme where I could set the global stuff
   in app_globals, and the circuit specific stuff in app_locals.

Thanks in advance for some insight.

-Erik
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at 
http://www.fusionauthority.com/bkinfo.cfm

Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists

Reply via email to