RE: searching for TLDs incorrectly

From: Mayo (mayo@nfy.ca)
Date: Sat Mar 02 2002 - 15:10:01 EST


You could do:

newlookup => 1

If the reseller chooses to use the lookups that are not validated on
their side, but speed up the lookups themselves, they can go with that,
if

newlookup => 0 (or not present at all), the old style lookup could be
used, and thus not affecting any reseller. This wouldn't really affect
the API not the old client versions.

mayo

> -----Original Message-----
> From: owner-dev-list@opensrs.org
> [mailto:owner-dev-list@opensrs.org] On Behalf Of Charles Daminato
> Sent: March 2, 2002 5:49 AM
> To: Christopher Hicks
> Cc: OpenSRS dev-list
> Subject: Re: searching for TLDs incorrectly
>
>
> We're working on a solution that will not drastically alter
> the API (we do
> have many legacy resellers to keep in mind)
>
> However, as an enhancement (addition, not alteration) to the
> API, I'll see
> what I can do here :)
>
> Charles Daminato
> TUCOWS Product Manager
> chuck@tucows.com
>
> On Sat, 2 Mar 2002, Christopher Hicks wrote:
>
> > On Sat, 2 Mar 2002, John Keegan wrote:
> >
> > > This issue seems to affect prefixes as well as suffixes,
> > > tucows.com.com is available... tucows.com.com.com is also
> available,
> > > and so on, and so on.
> >
> > Could we change the protcol to have two fields for the
> domain lookup?
> > domain => 'tucows',
> > tld => 'com',
> >
> > Since neither should contain periods it should be very fast
> to check for
> > it.
> >
> > --
> > </chris>
> >
> > "Outside of a dog, a man's best friend is a good book.
> > Inside of a dog, it's too dark to read." - Groucho Marx
> >
> >
>
>



This archive was generated by hypermail 2.1.3 : Tue Oct 19 2004 - 23:37:04 EDT