"FromTheRafters" <erratic.howard@gmail.com> wrote in
news:j17351$f14$1@dont-email.me:

> "Dustin" <bughunter.dustin@gmail.com> wrote in message
> news:Xns9F3492CC0679AHHI2948AJD832@no...
>> "FromTheRafters" <erratic.howard@gmail.com> wrote in
>> news:j0vo66$mt0$1 @dont-email.me:
>>
>>> "Dustin" <bughunter.dustin@gmail.com> wrote in message
>>> news:Xns9F31D2724E994HHI2948AJD832@no...
>>>> G. Morgan <G_Morgan@easy.com> wrote in
>>>> news:jkl537puukrjda1tsqi8fu0pl3qnbvkvde@Osama-is-dead.net:
>>>>
>>>>> ~BD~ wrote:
>>>>>
>>>>>>To *GET* the text file, one *has* to visit a URL.
>>>>>
>>>>> Or use the command line 'wget' in a sandbox, for the paranoid.
>>>>
>>>> Or use the sites known IP and forget the "URL" altogether...
>>>
>>> Isn't it still a URL even if you use the numerical address
>>> instead of a name to look up? )
>>
>> Nope. URL is a name, IP is an.. You guessed it, IP! URL requires
>> DNS help, actual IP doesn't.
>
> This time, I'll have to agree with Wikipedia:
>
> http://en.wikipedia.org/wiki/Uniform_Resource_Locator
> "Every URL consists of some of the following: the scheme name
> (commonly called protocol), followed by a colon, then, depending on
> scheme, a domain name (alternatively, IP address), a port number,
> the path of the resource to be fetched or the program to be run,
> then, for programs such as Common Gateway Interface (CGI) scripts, a
> query string,[8][9] and an optional fragment identifier.[10]
>
> The syntax is
> scheme://domainort/path?query_string#fragment_id"
>
> They are in total agreement with what I had already understood to be
> the case, so I like their answer better than yours. It is *still* a
> URL whether a domain name (or other name) to IP address lookup is
> needed or not.

If your using the IP address, a domain name lookup (resolve URL to IP)
seems a bit redundant.


--
I am a sinner
Hold my prayers upto the sun
I am a sinner
Heaven's closed for what I've done.