> An absolute file system path? Or absolute path as in the full > URL, including protocol? Damn it, now I'm confused. I get > the point though, I think, if you mean a site where you have > to replace /something with /somethingelse all over the place.
No, I simply meant that if you copy a web page from one server to another, absolute URLs to things on the first server will still resolve, while any other sort of URLs won't. > That's why I too like the "set the paths in the application.cfc" > type deal, since you gotta have 'em usually anyways. Why not > use variables and change them instead. :-) That's fine, if you're writing programs instead of static HTML documents. But this is a problem that can affect HTML documents, of course. > Is that the point of site relative paths? I can dig that. I > was just being thick headed. But I still, in the context of > the browser, site root relative and absolute are the same > thing. ... The point is to be able to say "site-root-relative" instead of "something that is absolute within the context of my server, but relative within the context of multiple servers". Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:239112 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
