From mboxrd@z Thu Jan 1 00:00:00 1970 From: Scott Schwartz To: 9fans@cse.psu.edu Subject: Re: [9fans] an idea Message-ID: <20040427014413.GA21542@bio.cse.psu.edu> References: <499f328d8dc6462edbadb7e4894feaf8@vitanuova.com> <05f311ed4273f9fdadc5f3453a807fed@plan9.escet.urjc.es> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <05f311ed4273f9fdadc5f3453a807fed@plan9.escet.urjc.es> User-Agent: Mutt/1.4.2.1i Date: Mon, 26 Apr 2004 21:44:13 -0400 Topicbox-Message-UUID: 6f427940-eacd-11e9-9e20-41e7f4b1d025 On Mon, Apr 26, 2004 at 09:57:05AM +0200, Fco. J. Ballesteros wrote: > But this could be done by arranging the the final clients to talk to the > actual servers, without resorting to proxy places. But this would require > changing the name space semantics. We do that for Plan B, but don't know > how it would fit with Plan 9. To make it more clear what I mean, > one way to do it would be to make all 9P servers become network addressable, > then change the way the ns is printed so that a user could reproduce the > ns from any other place in the network. Without understanding all the details, it seems like that breaks a feature of Plan 9, namely that namespaces work somewhat like lexical scoping, where some things just plain aren't visible from the outside. It seems like exporting a local name could be thought of somewhat like a functional closure, where you'd have some opaque cookie to be shared with friends that referred directly to the things in your scope, but that you couldn't generate from outside the namespace. If I recall correctly, Amoeba did something like that. Also, Prospero had some idea of closure, but I can't remember how that actually worked.