From owner-freebsd-hackers Sat Oct 28 15:54:10 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id PAA07643 for hackers-outgoing; Sat, 28 Oct 1995 15:54:10 -0700 Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id PAA07637 for ; Sat, 28 Oct 1995 15:54:07 -0700 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA02954; Sat, 28 Oct 1995 15:43:16 -0700 From: Terry Lambert Message-Id: <199510282243.PAA02954@phaeton.artisoft.com> Subject: Re: New lmbench available (fwd) To: hasty@rah.star-gate.com (Amancio Hasty Jr.) Date: Sat, 28 Oct 1995 15:43:15 -0700 (MST) Cc: terry@lambert.org, rcarter@geli.com, jkh@time.cdrom.com, hackers@FreeBSD.org In-Reply-To: <199510282149.OAA10066@rah.star-gate.com> from "Amancio Hasty Jr." at Oct 28, 95 02:49:52 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1767 Sender: owner-hackers@FreeBSD.org Precedence: bulk > > Novell's servers have no means of anonymity. > > > > Novell's servers must also go to a particular location to look up > > a resource identity. That leaves the location as a bottleneck. > > > > Novell's servers are broken. > > You mean that Novell does not have a mechanism to search for a > service in a network. So lets say that if I wanted to print to > a "lan" printer and I don't care where it is , it can't do that?? I'd like to see you replicate the buildings only color printer. 8-). A print queue is "a service on a server". The distinction is impossible to abstract for physicality. The services I'm talking about are things like "the next 1024 frames of 'Batman Returns'" or "the latest release of pkzip". Physical devices are peripherals to the network; they are not contained within the network. Content-based addressing can only work for things that are *within* the network. In theory, you could not care where the queue that you are printing to or where the printer servicing that queue resizes (assuming a pull model for print queuing). But you always care where the printer lives, just as you care where your floppy drive and CDROM drive (and maybe a tape drive) lives. Services based on data retrieval, on the other hand, are not dependent on the locality of the storage device containing the data, only the timeliness of its arrival at the requesting location. Ie: I can't afford packet transfer times exceeding my pool retnetion time for my video data. This discussion is probably getting too arcane for the general list readership; we should probably move it to private email. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.