PCButts Infamous Pic of Dust**** Relaxing After Virus Writing

[FromTheRafters]

"David H. Lipman" <DLipman~nospam~@Verizon.Net> wrote in message
news:j173ll0tfr@news6.newsguy.com...
> From: "FromTheRafters" <erratic.howard@gmail.com>
>
>>>>
>>>> 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.
>>
>
>
> When does a URL become an IRL ?
>
> Local protocols like hcp ?
> Ex: hcp://system/HomePage.htm

I don't know, maybe when localhost (127.0.0.1) is assumed by the protocol?

I refer to RFC 1738 now:

"host
The fully qualified domain name of a network host, or its IP
address as a set of four decimal digit groups separated by
".". Fully qualified domain names take the form as described
in Section 3.5 of RFC 1034 [13] and Section 2.1 of RFC 1123
[5]: ..."

> BTW: That syntax is incomplete:
> scheme://userassword@hostort/path

Yes, this is in agreement with rfc 1738 and the "host" section excerpted above.

[~BD~]

Dustin wrote:
> In that case, I am sorry for having wrongly accused you and for
> misunderstanding what you wrote.

<Gulp>

That's so good to hear! :-)

[Aardvark]

On Mon, 01 Aug 2011 22:11:58 +0100, ~BD~ wrote:

> Dustin wrote:
>> In that case, I am sorry for having wrongly accused you and for
>> misunderstanding what you wrote.
>
> <Gulp>
>
> That's so good to hear! :-)

At least he can give a sincere and unconditional apology when he finds
himself in the wrong, ****.

You certainly can't.



--
"Those who do not make human beings the center of their concern soon
lose the capacity to make any ethical choices, for they willingly
sacrifice others in the name of the politically expedient and
practical." - Dwight Macdonald, “The Root Is Man.�

[David H. Lipman]

From: "FromTheRafters" <erratic.howard@gmail.com>

> "David H. Lipman" <DLipman~nospam~@Verizon.Net> wrote in message news:j173ll0tfr@news6.newsguy.com...
>> From: "FromTheRafters" <erratic.howard@gmail.com>
>>
>>>>> 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.
>>>
>> When does a URL become an IRL ?
>>
>> Local protocols like hcp ?
>> Ex: hcp://system/HomePage.htm
>
> I don't know, maybe when localhost (127.0.0.1) is assumed by the protocol?
>
> I refer to RFC 1738 now:
>
> "host
> The fully qualified domain name of a network host, or its IP
> address as a set of four decimal digit groups separated by
> ".". Fully qualified domain names take the form as described
> in Section 3.5 of RFC 1034 [13] and Section 2.1 of RFC 1123
> [5]: ..."
>
>> BTW: That syntax is incomplete:
>> scheme://userassword@hostort/path
>
> Yes, this is in agreement with rfc 1738 and the "host" section excerpted above.

I think I have it.

A URL is all forms such as hcp://xxxxx That why it it is a Universal Resource. Its the
overarching concept.
A IRL is a subset limited to network protocols. That why it it is a Internet Resource.

http://en.wikipedia.org/wiki/Internet_Resource_Locator


--
Dave
Multi-AV Scanning Tool - http://multi-av.thespykiller.co.uk
http://www.pctipp.ch/downloads/dl/35905.asp

[David H. Lipman]

From: "Dustin" <bughunter.dustin@gmail.com>

> "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.


Using an alias (ex: google.com ) is implicit

Using an IP address (ex: 74.125.93.99 ) is explicit

One can have problems with the implicit such as in the case of a multi-homed node or, as I
think I mentioned earlier, when a host hosts multiple sites.

--
Dave
Multi-AV Scanning Tool - http://multi-av.thespykiller.co.uk
http://www.pctipp.ch/downloads/dl/35905.asp

[G. Morgan]

Dustin wrote:

>> Well, while you're deciding I guess it's time to renew to deal or
>> cancel it. Your choice.
>
>And you'll do what exactly?

Honor the deal and not mention you (even by innuendo) or reply to you,
and you do the same. That was the deal.

[FromTheRafters]

"David H. Lipman" <DLipman~nospam~@Verizon.Net> wrote in message
news:j17eem015fp@news6.newsguy.com...
> From: "FromTheRafters" <erratic.howard@gmail.com>
>
>> "David H. Lipman" <DLipman~nospam~@Verizon.Net> wrote in message
>> news:j173ll0tfr@news6.newsguy.com...
>>> From: "FromTheRafters" <erratic.howard@gmail.com>
>>>
>>>>>> 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.
>>>>
>>> When does a URL become an IRL ?
>>>
>>> Local protocols like hcp ?
>>> Ex: hcp://system/HomePage.htm
>>
>> I don't know, maybe when localhost (127.0.0.1) is assumed by the protocol?
>>
>> I refer to RFC 1738 now:
>>
>> "host
>> The fully qualified domain name of a network host, or its IP
>> address as a set of four decimal digit groups separated by
>> ".". Fully qualified domain names take the form as described
>> in Section 3.5 of RFC 1034 [13] and Section 2.1 of RFC 1123
>> [5]: ..."
>>
>>> BTW: That syntax is incomplete:
>>> scheme://userassword@hostort/path
>>
>> Yes, this is in agreement with rfc 1738 and the "host" section excerpted
>> above.
>
> I think I have it.
>
> A URL is all forms such as hcp://xxxxx That why it it is a Universal
> Resource. Its the overarching concept.
> A IRL is a subset limited to network protocols. That why it it is a Internet
> Resource.
>
> http://en.wikipedia.org/wiki/Internet_Resource_Locator

Thanks for the link, but as is often the case I find the rfc to be better
written than the Wiki article.

My take on it is that both URL and IRL are both restrictions of the overarching
Resource Locator concept. They both seem to be designed for the "Internet"
as opposed to the more general locator. I'll have to read further to assess what
any differences might be. I'm guessing at this point that the differences are in
the syntactical requirements' further restrictions in the URL.

[Bullwinkle.]

Nor can Socialist mooching Scum.


"Aardvark" <aardvark@youllnever.know> wrote in message
news:j17dlg$laj$2@dont-email.me...
On Mon, 01 Aug 2011 22:11:58 +0100, ~BD~ wrote:

> Dustin wrote:
>> In that case, I am sorry for having wrongly accused you and for
>> misunderstanding what you wrote.
>
> <Gulp>
>
> That's so good to hear! :-)

At least he can give a sincere and unconditional apology when he finds
himself in the wrong, ****.

You certainly can't.

[Bullwinkle.]

Recess time over?


"G. Morgan" <G_Morgan@easy.com> wrote in message
news:05he37tekn5ecr2fpj81nnfr8clrmju25d@Osama-is-dead.net...
Dustin wrote:

>> Well, while you're deciding I guess it's time to renew to deal or
>> cancel it. Your choice.
>
>And you'll do what exactly?

Honor the deal and not mention you (even by innuendo) or reply to you,
and you do the same. That was the deal.

[Nobody > (Revisited)]

On 7/26/2011 4:21 AM, FromTheRafters wrote:
> "~BD~"<~BD~@nomail.afraid.com> wrote in message
> news:h4qdnUKcPrr7BLPTnZ2dnUVZ8qKdnZ2d@bt.com...
>
>> Who gives the MVP's the right to act as judge, jury and executioner?
>
> It's just a hosts file, people can choose as they wish.
>
> It's funny though that someone who claims to be an MVP
> has his own sites blocked by the MVP's hosts file.
>
>

Tis funny... I have a BARE HOSTS file and it's blocked here.

Avast? Temp disable... NO (But I webrepp'ed it as nasty, pr()n and warez)

Malwarebytes Antimalware (paid version, resident) Yup!

--
"**** this is it, all the pieces do fit.
We're like that crazy old man jumping
out of the alleyway with a baseball bat,
saying, "Remember me mother****er?"
Jim “Dandy” Mangrum