Posts: 3,621
Name: Thierry
Location: I'm the uber Spaminator !
|
Quote:
Originally Posted by Mooofasa
|
Not in my definition.
An URL would be a reference to a document (host+port+pathname), with it's protocol, but without any search or hashes values.
An URN would be the reference to a document, with it's search and hash fields (if any), but without the protocol.
And the URI is the complete chain: The protocol, the document, and the search/hash values.
And for the sake of reference:
Quote:
In general, a URI has this form:
protocol//host:port/pathname#hash?search
For example:
http://home.netscape.com/assist/extensions.html#topic1?x=7&y=2
These parts serve the following purposes:
- protocol represents the beginning of the URL, up to and including the first colon.
- host represents the host and domain name, or IP address, of a network host.
- port represents the communications port that the server uses for communications.
- pathname represents the URL-path portion of the URL.
- hash represents an anchor name fragment in the URL, including the hash mark (#). This property applies to HTTP URLs only.
- search represents any query information in the URL, including the question mark (?). This property applies to HTTP URLs only. The search string contains variable and value pairs; each pair is separated by an ampersand (&).
|
The only time I have an use for the URI value, is when I use an URL rewriting scheme. In that case, the URL on the server side is the rewritten one.
If I need to access what exactly was typed, I need to address the URI.
I needed that because I had rewrote the standard name=value scheme on a specific site.
The url's where like http://whatever.com/profile/page:1|s:3
And I needed to parse the URI to find back the "page:1|s:3" values.
__________________
Only a biker knows why a dog sticks his head out the window.
Last edited by tripy; 02-02-2008 at 07:57 PM..
|
Maybe they ask Alan to encode plain text to confuse lame people and keep them away from 
