Toby Inkster wrote:
> Steve Pugh wrote:
>
>> Because both URLs point to the same resource
>
> It is amazing the number of people that don't seem to "get" URLs --
> especially relative URLs with lots of back references.
>
> "http://example.org/a/b/c/d/foo.html"; references "../e/f/../g/bar.html"
> which results in "http://example.org/a/b/c/e/g/bar.html";.
>
> This seems so obvious to me, but to some people (who often seem quite
> knowledgable from their posts on other topics) it seems to be a real
> problem.
>
> Perhaps this is because I grew up around the command line?
>
> It would be good if there were a really comprehensive tutorial on URLs
> to which we could refer people. Anyone know of any? Or am I going to have
> to write one?
It doesn't have high potential for readership. Web designer prefer to extend
knowledge on CSS and the visuals.
You must be thinking about a guide for Perl programmers, but that group
already has suitable background. It is 600 page books like *this*
(http://www.tldp.org/LDP/abs/html/) that discourages people from ever
beginning to learn and practice.
Roy
--
Roy S. Schestowitz
http://Schestowitz.com
|
|
