Why REST API and what qualifies as a REST API (load balancing + whois)


Well as REST API (Application programmable interfaces) go they are one that are mainly URL or form method POST directive only, part of the reason they are like this for example say you have a whois intensive application and for some reason some of the domain nics are rejecting your IP cause of two main lookup what you do is for example you made http://whois.snails.email you would then make on independant IP addresses the following for example remember whois api is not a heavy load so it can sit on multiple of your IP addresses without a question what you do is have the following where each of these are in an independant IP address:

Where you then make whois.snails.email redirect to a selection based and shuffled on their query source referee URL IP Address or $_SERVER[‘REMOTE_ADDR’] which has a cache that redirect each to each one once dropping that from the list to do until the listing refreshes, to bounce the queries around coming from different IP addresses this would be done in the whois.snails.email with:

 <?php header('Location: http://1.whois.snails.email/v2/bluehost.com/json.api'); ?>

where cURL and the rest will redirect to this and get the query result.

Advertisements