This is all possible, but currently we don't locally hold the status.
Since we have over 3.5 million domains in our inventory, getting a local
status could take considerable time - we're working on a better solution
(remember, that's also an additional 3.5mil+ DB entries, even if it's a
simple field in a table)
Charles Daminato
TUCOWS Product Manager
chuck@tucows.com
On Wed, 29 May 2002, Kai Schaetzl wrote:
> > Anyway, we could always store the data locally and put a *NOTE* on the
> > search page saying that the results may not be authoritative and querying
> > the domain directly would show the "real goods"
> >
>
> What about a "cron-like" feature in the background which would check that
> the registry lock status is the same as the local lock status (the latter
> being authoritative). Put a check mark there to get it going for one pass
> and then do it within your discretion within a day and send a confirmation
> email when it's finished.
> Similarly, for caching the lock status locally, we could submit a request
> and next day it's cached. I assume many resellers will never even think
> about using it, so you avoid a lot of traffic and ressource drain.
> Also, to avoid heavy peak traffic you could use a similar background script
> to implement "lock all domains". We just submit it and your application
> does it in the background and sends a confirm message when it's done.
>
>
> Kai
>
> --
>
> Kai Schätzl, Berlin, Germany
> Get your web at Conactive Internet Services: http://www.conactive.com
> IE-Center: http://ie5.de & http://msie.winware.org
> ClubWin - Help for Windows Users: http://www.clubwin.com
>
>
>
>
This archive was generated by hypermail 2.1.3 : Tue Oct 19 2004 - 23:37:15 EDT