3 ms·
It's tough because it's not as difficult as you might imagine to get your IP address rate limited. If a lot of people were using it at once and I was sending ou
by grinnick 14y ago
It's tough because it's not as difficult as you might imagine to get your IP address rate limited. If a lot of people were using it at once and I was sending out hundreds of availability checking requests I'd probably hit the limits.
For example, I had this hosted on Heroku for a while and tons of requests were failing because Heroku uses shared IP addresses for all the sites it hosts. Evidently I wasn't the only person doing domain availability checks from their network.
Also, the UI would get pretty nuts right?
- firloop 14y agoIs it possible to run the domain availability checks from the client-side with AJAX?
- grinnick 14y agoNot sure to be honest but probably not. My availability checks eventually go through this ruby gem: http://www.ruby-whois.org/ http://www.ruby-whois.org/ Basically it just does a whois lookup on the domain and I don't think I could replicate that behavior from the client side. Edit: This comment says it would be possible http://news.ycombinator.com/item?id=5132750 http://news.ycombinator.com/item?id=5132750
- raylu 14y agoBut not client-side. Still, better to just do a DNS lookup (not rate-limited) than WHOIS.