I see. But that doesnt mean they have to have every .somthing. A gaming company named bungie has a website and it is bungie.net, it dosnt have bungie.com or anything. So they could have itun.com
They actually do have bungie.com, just FYI
I see. But that doesnt mean they have to have every .somthing. A gaming company named bungie has a website and it is bungie.net, it dosnt have bungie.com or anything. So they could have itun.com
Why do we still need to show "http://"? Can't it go away like the need for "www"?
There's no need to show it, Chrome doesn't in the address bar nor is it obligatory to show it on the text displayed for the link. But for the actual link reference, it needs to be there, otherwise, how does the browser know to use http and not https, ftp, ftps, sftp, telnet, mailto or other protocols to threat the link info ?
There was a need for www ? When was this ? www was never needed. It's just that convention everyone used out of habit. It's just a DNS entry that points to an IP address, it had no special function and still doesn't.
You mean like back in the days when forums were read using an NNTP reader ? Back when chat was done using IRC software ? Back when remotely logging into a server was done over Telnet ?
You mean we're going back to the good old days of the Internet, back when the Web browser was used to browse the web and not to try to be a swiss army knife ?
Goodie.
Unfortunately, you're reading it wrong. Those apps all still use the "URLs" and all the domain name infrastructure. It's just hidden away. Also, all those apps are just very specialized web browsers in a sense, they just don't use hypertext but XML. If things continue to devolve the way they have, soon the entire Internet will exclusively use the HTTP protocol for everything. Heck, in the same vein as XML, we could just rename HTTP for XTP (eXtensible Transfer Protocol) and do away with any pretension of multi-protocol over a network of networks.
Its pretty clever.
I assume Microsoft will respond with a domain from the Hitachi islands and bring out http://zunis.hit/ prefix
What I'm saying is that the web has become a tangled mess. And the URL structure just isn't good for the general public and DNS itself is a mess (and DNS names aren't in the control of the content providers).
Displaying something is a different thing than requiring it. Firefox will automatically pre-pend "www." and post-pend ".com" if you just type a dot-less text string into the URL bar - that doesn't mean those parts of the address are unnecessary;
caccamolle said:I was hoping that Apple would not join in the twitcrapology ... but again, it does reflect upon Apple's transformation in recent years, very effectively indeed.
I think the point he was going for was that ITUN is a spanish company and .es is typically used for spanish sites.
Cry me a river.Welcome to the Apple Consumer Eletronics Era.
Oh really? To which ccTLD (country code top-level domain) does .s refer?or...or... itn.s
This could go on for a bit as you'd imagine.
Wirelessly posted (Mozilla/5.0 (iPhone; U; CPU iPhone OS 4_2_1 like Mac OS X; en-us) AppleWebKit/533.17.9 (KHTML, like Gecko) Version/5.0.2 Mobile/8C148 Safari/6533.18.5)
Welcome to the Apple Consumer Eletronics Era.
Cry me a river.
You're missing my point. What I'm saying is that the web has become a tangled mess.
And the URL structure just isn't good for the general public
and DNS itself is a mess (and DNS names aren't in the control of the content providers).
But as the concept of Apps get bigger, endusers will use them instead.
Instead of telling people to go to www.cnn.com, CNN can direct people to their App. Also those App providers do not have to use DNS names, they can embed actual IP addresses.