Seems like each circuit could have it's own imagesroot couldn't it?
If you're using dot notation to distinguish the circuit, why not just
add a .images to it.... like this:
<cfset request.search.images="http://images.funkynat.com/search">
<cfset request.products.images="http://images.funkynat.com/products">
hmmmmmmmmmmmmmmmmm.....
That only works if your images are off the CF server, which is good, but
not practical when getting started. Makes things harder.
Steve Nelson
http://www.SecretAgents.com
Tools for Fusebox Developers
Nat Papovich wrote:
>
> 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
