Hacker News new | past | comments | ask | show | jobs | submit login

That you've been 'able to deal with it' is simply because that's what you are used to, but that does not mean that that is better or worse, simply a way of life.

Anyway, anything I search for with 'order' and 'domainname' wants to sell me domains, so no citations, but the basic complaint was that it breaks the sequence of a url, where the 'highest' entity should be on the left, and the smallest entity on the right.

So, iirc, the optimimum would have been something like:

http/com/ibm/www/80/somepath/somefile

That wasn't it exactly, but it gives the general idea.

The DNS was long established by the time URLS rolled around so I doubt anything could have been done about it anyway.

If the phishing troubles resulting from the DNS order would have been foreseen I'm pretty sure that they would have picked the 'other' way.

edit:

found something about all this after some digging:

http://answers.google.com/answers/threadview/id/754114.html

http://bandb.blogspot.com/2009/01/are-domain-name-backwards....

Since the DNS is a hierarchical system, the 'root' of the hierarchy should have been at the beginning, just like in unix you don't start with the name of the file but with the 'root'.

Anyway, the quote I'm looking for is by none other than Tim Berners-Lee, I think it may have been in his book though, not online.




you'd have to have at least a protocol/host/path separator.

http/com/ibm/www/80/somepath/somefile -> is this referring to http://ibm.com/www... or http://www.ibm.com/80...

Instead, I would imagine it should be something like:

com.ibm:http/80:/somepath

You could even do a lookup to com.ibm and ask for http SRV record to find the actual host to connect to.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: