bill
msg:4088713 | 3:06 am on Feb 28, 2010 (gmt 0) |
If the domain name changes IPs in the future you would have trouble.
|
johnmoose
msg:4088893 | 3:01 pm on Feb 28, 2010 (gmt 0) |
That's the whole idea of DNS, no need to worry about the IP address. And people remember names a whole lot easier than 12 digit numbers. Its the phone book of the Internet.
You can do it, if its only for local hostnames and you host them yourself. But the client does cache IP resolved addresses too for a certain amount of time. So its only the first time resolving that takes a couple of milliseconds, the second time it should be cached locally (be that on disk or in memory).
|
maximillianos
msg:4088915 | 4:54 pm on Feb 28, 2010 (gmt 0) |
I think it is an interesting idea, and it might save you some time, but like others said, it is risky and adds a layer of maintenance.
You would have to stay on top of the current IP addresses for all domains you did this for, and update accordingly.
That, or you could schedule a job to monitor it and have it run ever 10 minutes or something and use it to keep a "live" cached copy yourself of the IP addresses... That would work.
|
KenB
msg:4088938 | 6:00 pm on Feb 28, 2010 (gmt 0) |
Using the IP address could be a "poor mans" means of putting files that support a webpage on a "cookieless" domain, which is one way to speed up page loading. The key would be to be the one that controls the IP address and for it to be a dedicated IP for your website.
Thoughts on this?
|
claus
msg:4088950 | 6:27 pm on Feb 28, 2010 (gmt 0) |
Back in the old days when I started using the internet, IP-addresses in URLs were very common. It was only later, with the emergence of www, that "vanity" domain names started to get popular. So, yes of course you can use IP-addresses :)
- what does this mean?
|
mattur
msg:4088958 | 6:43 pm on Feb 28, 2010 (gmt 0) |
a "cookieless" domain
- what does this mean?
|
|
Serving static content from another domain to prevent main-domain cookies being sent with each request, thereby minimising request overhead [code.google.com]
|
|
