Re: centroid propagation

Mark Prior <> Mon, 18 October 1993 00:38 UTC

Received: from by IETF.CNRI.Reston.VA.US id aa20187; 17 Oct 93 20:38 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa20181; 17 Oct 93 20:38 EDT
Received: from by CNRI.Reston.VA.US id aa16140; 17 Oct 93 20:38 EDT
Received: by (4.1/UCD2.05) id AA00537; Sun, 17 Oct 93 17:10:53 PDT
Received: from by (4.1/UCD2.05) id AA00459; Sun, 17 Oct 93 17:09:00 PDT
Received: by with SMTP (5.61+IDA+MU/UA-5.28) id AA18277; Mon, 18 Oct 1993 09:40:23 +0930
Message-Id: <>
To: Hiroaki Kashima <>
Subject: Re: centroid propagation
In-Reply-To: Your message of "Fri, 15 Oct 1993 23:01:28 +0900." <>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Mon, 18 Oct 1993 09:40:22 +0930
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Mark Prior <>

     >  PERL and WAIS
     >  Martin Hamilton <>
     >  whois++ ->

This implementation is really mine and it's a gateway to an underlying
X.500 Directory Service.

     I've found kth's implementation has a mechanism for centroid
     propergation. But others don't seem to have that mechanism. Do they
     use DB system to change data and centroid propergation?

I don't support centroids since it is too difficult to do a complete
implementation when you are constrained by another system that doesn't
map into whois++ cleanly. I would attempt to do a partial
implementation but unless whois++ supported "maybe" style responses
this would be too confusing for the user.

The data management of my system is handled by X.500 and so the
whois++ server is only a readonly interface onto the data.