From owner-freebsd-current Thu Dec 31 11:05:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA05394 for freebsd-current-outgoing; Thu, 31 Dec 1998 11:05:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA05383 for ; Thu, 31 Dec 1998 11:05:17 -0800 (PST) (envelope-from dboreham@netscape.com) Received: from dredd.mcom.com (dredd.mcom.com [205.217.237.54]) by netscape.com (8.8.5/8.8.5) with ESMTP id LAA17017 for ; Thu, 31 Dec 1998 11:04:56 -0800 (PST) Received: from netscape.com ([208.12.63.45]) by dredd.mcom.com (Netscape Messaging Server 4.0) with ESMTP id F4UFO800.QMV for ; Thu, 31 Dec 1998 11:04:56 -0800 Message-ID: <368BCBE7.BCC1FFB5@netscape.com> Date: Thu, 31 Dec 1998 11:09:27 -0800 From: dboreham@netscape.com (David Boreham) X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: Re: NOW/MOSIX/Beowulf Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <76ec7v$1rh$1@FreeBSD.csie.NCTU.edu.tw>, shmit@kublai.com (Brian Cully) wrote: > On Wed, Dec 30, 1998 at 12:55:02PM -0800, Mike Smith wrote: > > Cool; thanks for the review. Anyone else using either the Netscape > > server or experimenting with the OpenLDAP implementation are invited to > > speak up; this sort of input's really useful. This is an interesting thread. One point which should be made, and I've not seen made is that the protocol (LDAP) needs to be discussed separately from the server implementation (e.g. Netscape, Novell). One might argue that LDAP server implementation XYZ is inefficient in some respect, but that an efficient LDAP server for the task at hand could be build. For example, those planning to roll their own authentication service might be well served by using a subset of the LDAP protocol, but building their own server, rather than inventing a new world from scratch. > I've done the evaluation here for the Netscape server, and was > fairly unimpressed even though we had a simple setup (no distributed > servers, for example, and from what I understand, this is where > Netscape's main problems lie). The current Netscape LDAP server supports multi-server replication where each distinct DIT subtree must be mastered on one and only one server. Thus read load can be distributed across multiple replication consumers easily. To partition the data, in order to for example constrain the size of the working set of each server, you currently need to have an intelligent client. The client needs to have some knowledge of the partitioning scheme in order to locate the server which contains the target entry. Perhaps this is what you mean ? > I've heard some very good things about OpenLDAP, but we haven't > recieved our eval copy yet. But from reading the literature about > the design and implementation, it sounds really sweet. Curious. OpenLDAP represents ongoing development of the University of Michigan LDAP server code base. This was also the basis for the Netscape product. Essentially the two share the same design and implementation (albeit diverged over a period of three years). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message