|
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
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.