From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <ee9e417a0601021834i45b280a3jc73fe1c00a901728@mail.gmail.com>
Date: Mon,  2 Jan 2006 21:34:42 -0500
From: Russ Cox <rsc@swtch.com>
To: erik quanstrom <quanstro@speakeasy.net>,
	Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] authentication by LDAP?
In-Reply-To: <20060103021355.6E49B1E4139@dexter-peak.quanstro.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <faaa980a2065101fa62467283fa420a1@quintile.net>
	<20060103011226.4BAC31E4137@dexter-peak.quanstro.net>
	<ee9e417a0601021715h1d6e93f1g702f379bf0c3cd31@mail.gmail.com>
	<20060103021355.6E49B1E4139@dexter-peak.quanstro.net>
Cc: 
Topicbox-Message-UUID: cddb4b78-ead0-11e9-9d60-3106f5b1d025

> if one wrote an ldap fileserver that served up ndb-stype tuples in a stan=
dard
> format, all the ndb library would need is a hook to talk to this fileserv=
er instead
> of parsing an ndb file. you could do the same with dns and other protocol=
s.

yes.  and steve was saying that the hook could be
you mount the file server somewhere and then use
the name of its ndb file in /lib/ndb/local.  ndb can just
access a file like it always has been, never caring
what kind of file server provides the file.

russ