[prev] [thread] [next] [lurker] [Date index for 2003/09/03]
On 3 Sep 2003 at 2:20, Simon Cozens wrote: > Mark Fowler: > > I hate software that doesn't map http://theirdomainname.com to > > http://www.theirdomainname.com. > > simon-cozens.org is The Only A Record for my web site, and rightfully > so. Why the hell do you think you need a www. to tell you you're > getting the site via the World Wide Web? Because some people think that domain names shouldn't be host names? www.example.com is, conceptually (at least for me), a host named 'www' in the domain 'example.com'. example.com is, um a host name '' in the domain 'example.com'? > If it's a web server, where else is it going to be? On a host that has a name separate from its domain name? Whether it's called "www" or "web" (as in http://web.mit.edu/ -- though they seem to have switched over to www.mit.edu the last time they looked; originally, that hostname wasn't used at all, then it was some student organisation) or "welcome" isn't that important. > What next? rsync://rsync.foo.com? Why not? Funet's rsync services are on rsync.nic.funet.fi. But rsync://server123.foo.com would make sense to me, too. rsync://foo.com, not so much. > Do you ssh to ssh.yourhost.yourdomain.net? No, because "yourhost" is already a hostname, so I don't see a need to add "ssh" in front. Cheers, Philip -- Philip Newton <pnewton@xxx.xx>There's stuff above here
Generated at 14:02 on 01 Jul 2004 by mariachi 0.52