That's the outline, but of course the success comes in the tuning of the script.FC, when you connect to the server, I assume it works like
You: Connect
Server: Identify
You: Helo, Usernameassword
Server: Hello Username
You: Check Google
Server: available
You: Register google.co.uk
Server: OK / Error
You: Disconnect
Or something like that...
If you read the T&C's you'll find the limits, if you exceed the limits Nominet will block you, if you regularly exceed the limits you'll probably find yourself excludedDo you HAVE to check the domain is available or can you just send the 'register' command ?
If my trip to Nominet is 5ms and yours is 6ms, then my application can be nearly 1ms slower but still beat you as it has less time on the wireIf you can do that, then your latancy to is pretty much irrelevant ?
Test, try, retest, try, retest and repeat and repeat, this is the area that you are on your ownI have loads of idea's to boost responsiveness of DAC querying and registering names, but as I don't have access (as yet), I can't test any.
I would be surprised if anyone let you "play" with their account as if you break anything and get a block they will not be able to register names until that block expires.I'm going to ask my hosting company if I can jack his account for testing, as I he has a tag, but not sure on DAC access.
Nominet's limits work out at about 5 queries/second if you spread your query allocation over the whole 24 hour period or about 17/sec if you want to blow your allocation at the maximum rate, however in practise domains are released during the whole 24 hour period (I've caught names before 1am and also after 23:30).
There's also another 50-100 systems also competing against your system
Good luck!