From owner-freebsd-current Mon Mar 2 19:34:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA21562 for freebsd-current-outgoing; Mon, 2 Mar 1998 19:34:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA21509 for ; Mon, 2 Mar 1998 19:34:00 -0800 (PST) (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.8/CET-v2.2) with SMTP id DAA02985; Tue, 3 Mar 1998 03:25:59 GMT Date: Tue, 3 Mar 1998 12:25:59 +0900 (JST) From: Michael Hancock To: Terry Lambert cc: toor@dyson.iquest.net, smp@csn.net, opsys@mail.webspan.net, jak@cetlink.net, current@FreeBSD.ORG Subject: Re: 3.0-RELEASE? In-Reply-To: <199803030314.UAA10998@usr06.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 3 Mar 1998, Terry Lambert wrote: > > I just found out that ODI's ObjectStore uses Transitive Closure > > calculations to manage objects. They've got one of the fastest object db > > implementations around for this and other reasons. > > > > Also, have a look at byacc. > > Were you thinking of maybe "closure.c" and "warshall.c"? ;-). > > The "gprof", "tsort", and "make" code also use cycle detection... Yes. Another thing I found interesting about ODI is their distributed cache manager. The backend is basically dumbed down to just understand pages. But it keeps track of them and informs clients with cached pages whenever the server copy is dirtied. The server maintains a return socket for each client for the "upcall". Regards, Mike Hancock To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message