From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu, Russ Cox <rsc@swtch.com>
References: <faaa980a2065101fa62467283fa420a1@quintile.net>
	<20060103011226.4BAC31E4137@dexter-peak.quanstro.net>
	<ee9e417a0601021715h1d6e93f1g702f379bf0c3cd31@mail.gmail.com>
	<20060103021355.6E49B1E4139@dexter-peak.quanstro.net>
	<ee9e417a0601021834i45b280a3jc73fe1c00a901728@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
In-Reply-To: <ee9e417a0601021834i45b280a3jc73fe1c00a901728@mail.gmail.com>
Subject: Re: [9fans] authentication by LDAP?
Message-Id: <20060103025301.D63B41E4137@dexter-peak.quanstro.net>
Date: Mon,  2 Jan 2006 20:53:01 -0600
Cc: 
Topicbox-Message-UUID: cde1ede8-ead0-11e9-9d60-3106f5b1d025

i read to much into "in the form of flat files." i guess we're in noisy agreement.

- erik


Russ Cox <rsc@swtch.com> writes

| 
| > if one wrote an ldap fileserver that served up ndb-stype tuples in a standard
| > format, all the ndb library would need is a hook to talk to this fileserver instead
| > of parsing an ndb file. you could do the same with dns and other protocols.
| 
| 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