I use what Steve Nelson once suggested. Use the request.imgroot
like this:
<img src="#request.imgroot#/foo.gif">
If you use imgroot instead of fuse_root then you can easily move
your images to special images server when the load increases.
Example:
1) Images are on the same server:
request.imgroot = "/images"
2) Images are on a dedicated server:
request.imgroot = "http://images.foo.com/images"
Erki
----- Original Message -----
From: "Erik Voldengen" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, July 21, 2000 6:23 PM
Subject: RE: Images with nested fuseboxes
> I just put them in a top level folder, and refer to them by:
>
> <img src="#attributes.Fuse_Root#/images/category/foo.gif">
>
> I'm sure there are more elegant ways to do it, but this works
> pretty good.
>
> -Erik
> > In an effort to keep applications as portable as possible...
> > Has anyone found a good way to keep images for nested
> > fuseboxes local to
> > their respective applications?
> > Or, is everyone just dumping them into a local (relative to the
> > parent/top-level app) or mapped directory?
> >
> > Thanks for the info.
> > Phil
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
