I've got my images stored on a separate box, and use an #request.images_dir#
to refer to the actual location of these guys. Its worked like a champ. Fer
example, once upon a time the box with the images had to go down for a day,
so I just copied the images to a different webserver, and edited the value
of request.images_dir in app_globals.cfm. Worked slick and I didn't even
have to restart CF or nuthin'.
As for the dot notation and what not, I tend to avoid it. I normally mark up
any calls for page elements as "#request.website_dir#/{the
subfolder}/whatever.cfm". I've found it keeps things easier to manage when
I'm looking for what came from where...
Alan McCollough
Web Programmer
Allaire Certified ColdFusion Developer
Alaska Native Medical Center
> -----Original Message-----
> From: Nat Papovich [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, December 13, 2000 10:25 PM
> To: Fusebox
> Subject: RE: the dot notation
>
> Well well well.
>
> > <cfset request.imagesroot="http://images.funkynat.com">
> > <cfoutput>
> > <img src="#request.imagesroot#/products/156.gif">
> > </cfoutput>
>
> If I'm building the products app as a standalone, I don't think that I'm
> at
> http://images.funkynat.com/products. I think I'm a images.funkynat.com.
> Requiring any given app to know where it lives in the "rest" of the app I
> believe defeats the purpose of the dot notation and cfincluding indexes.
> To
> allow an index to be cfincluded willy-nilly, it cannot rely on anything
> outside it's own relative self. Am I right here? Can someone who's built
> one
> of deez suckers step up and explain?
>
> Namaste,
>
> Nat Papovich
> Webthugs Consulting
> ICQ 32676414
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
