RE: The proper way to set up your directory stucture forwebserving

If all of your images were in your common directory, then I'd use the
alias.  Otherwise, ../../common/i/imagename.jpg will work regardless or
if www is the root directory in your web server config,
/common/i/imagename.jpg.  

John A. Jones, CISSP
Americas Information Security Officer
Jones Lang LaSalle, Inc.
V: +1-630-455-2787  F: +1-312-601-1782
john.jones@xxxxxxxxxx

-----Original Message-----
From: rick baird [mailto:rick.baird@xxxxxxxxx] 
Sent: Tuesday, January 18, 2005 3:46 PM
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] The proper way to set up your directory stucture
forwebserving

On Tue, 18 Jan 2005 15:37:57 -0600, Jones, John (US)
<John.Jones@xxxxxxxxxx> wrote:
> I would do the first.  That way, any given app can refer to all of 
> it's parts via indirect links: ../images/header.jpg and
../html/index.html.
> Apps are also unaware of their root directory, i.e. live vs. test.
> They're also unaware of your application's naming convention.

<snip>

> Personally, I figure having HTML is the 'default' content of a 
> directory so I use:
> /www/app <-- html files
> /www/app/i <-- images
> /www/app/macro <-- net.data
> etc.

John,

I like that - except if i'm in '/www/app/macro', how would I display an
image out of '/www/common/i'?  - would that be an alias type mapping in
my server config?

Thanks,

Rick
_______________________________________________
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list To
post a message email: WEB400@xxxxxxxxxxxx To subscribe, unsubscribe, or
change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/web400.




This email is for the use of the intended recipient(s) only.  If you have 
received this email in error, please notify the sender immediately and then 
delete it.  If you are not the intended recipient, you must not keep, use, 
disclose, copy or distribute this email without the author's prior permission.  
We have taken precautions to minimize the risk of transmitting software 
viruses, but we advise you to carry out your own virus checks on any attachment 
to this message.  We cannot accept liability for any loss or damage caused by 
software viruses.  The information contained in this communication may be 
confidential and may be subject to the attorney-client privilege. If you are 
the intended recipient and you do not wish to receive similar electronic 
messages from us in future then please respond to the sender to this effect.