> ... and WWW. turns to be the bigger joker of all times, after all,
> several sites doesn't use it anyway (http://home.xxx.xxx, or
> http://anything.xxx)

Consider that the portion of the URL following http:// and up to the first /
following, is the name of a computer.  In a large computing environment,
consistently naming http servers with a www prefix appropriately identifies
these devices and the service(s) they provide.  It's unfortunate that web
publishers have deviated from this standard now creating confusion since you
no longer know whether "xyz.com" means www.xyz.com or _just_ xyz.com.
Although these two URLs can dereference into the same IP address, that now
effectively doubles the size of the DNS server's tables (if everyone
registered both forms of the URL).

Since the Internet is used for much more than just http traffic, it _is_
reasonable to uniquely identify those services with a standard prefix.

Mitch Miller, Omaha, NE
mdmiller2@home.com