RE: Transport requirements for DNS-like protocols

Patrik Fältström <paf@cisco.com> Sat, 29 June 2002 08:48 UTC

Return-Path: <ietf-irnss-errors@lists.elistx.com>
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GYG00H04LSLR0@eListX.com> (original mail from paf@cisco.com); Sat, 29 Jun 2002 04:48:21 -0400 (EDT)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GYG00H01LSLQY@eListX.com> for ietf-irnss@elist.lists.elistx.com (ORCPT ietf-irnss@lists.elistx.com); Sat, 29 Jun 2002 04:48:21 -0400 (EDT)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856) id <0GYG00H01LSKQX@eListX.com> for ietf-irnss@elist.lists.elistx.com (ORCPT ietf-irnss@lists.elistx.com); Sat, 29 Jun 2002 04:48:20 -0400 (EDT)
Received: from ams-msg-core-1.cisco.com (ams-msg-core-1.cisco.com [144.254.74.60]) by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0GYG00EIXLSKJT@eListX.com> for ietf-irnss@lists.elistx.com; Sat, 29 Jun 2002 04:48:20 -0400 (EDT)
Received: from xbe-ams-303.cisco.com (localhost [127.0.0.1]) by ams-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g5T8klL7014728; Sat, 29 Jun 2002 10:46:47 +0200 (MET DST)
Received: from xfe-ams-301.cisco.com ([144.254.75.88]) by xbe-ams-303.cisco.com with Microsoft SMTPSVC(5.0.2195.4453); Sat, 29 Jun 2002 10:47:31 +0200
Received: from [10.0.1.100] ([144.254.74.55]) by xfe-ams-301.cisco.com with Microsoft SMTPSVC(5.0.2195.4453); Sat, 29 Jun 2002 10:47:30 +0200
Date: Sat, 29 Jun 2002 10:11:15 +0200
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
Subject: RE: Transport requirements for DNS-like protocols
In-reply-to: <7FC3066C236FD511BC5900508BAC86FED21D3B@trestles.internal.realnames.com>
To: Nicolas Popp <nico@realnames.com>, 'Michael Mealling' <michael@neonym.net>, John C Klensin <klensin@jck.com>
Cc: Rob Austein <sra@hactrn.net>, ietf-irnss@lists.elistx.com
Message-id: <17823168.1025345475@localhost>
MIME-version: 1.0
X-Mailer: Mulberry/2.2.0 (Mac OS X)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-disposition: inline
References: <7FC3066C236FD511BC5900508BAC86FED21D3B@trestles.internal.realna mes.com>
List-Owner: <mailto:ietf-irnss-help@lists.elistx.com>
List-Post: <mailto:ietf-irnss@lists.elistx.com>
List-Subscribe: <http://lists.elistx.com/ob/adm.pl>, <mailto:ietf-irnss-request@lists.elistx.com?body=subscribe>
List-Unsubscribe: <http://lists.elistx.com/ob/adm.pl>, <mailto:ietf-irnss-request@lists.elistx.com?body=unsubscribe>
List-Archive: <http://lists.elistx.com/archives/ietf-irnss/>
List-Help: <http://lists.elistx.com/elists/admin.shtml>, <mailto:ietf-irnss-request@lists.elistx.com?body=help>
List-Id: <ietf-irnss.lists.elistx.com>
X-OriginalArrivalTime: 29 Jun 2002 08:47:30.0981 (UTC) FILETIME=[9ACA2D50:01C21F49]

--On 2002-06-28 10.24 -0700 Nicolas Popp <nico@realnames.com> wrote:

> As soon as you do fuzzy matching that forces you to retrieve
> multiple records and rank them, the operational complexity is increased
> ten-fold (and your query response time becomes way more inpredictable
> unless you do a few "right things").

Doing fuzzy-matching is most efficiently done by doing a calculation of a
hash on the search string (something like soundex) and then exact mathing
in the database.

So, fuzzy-matching is for me just another version of "preparation" of the
search string.

    paf