Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!emory!hubcap!rbrink
From: rbrink@hubcap.clemson.edu (Rick Brink)
Newsgroups: comp.protocols.appletalk
Subject: Re: System 7.0 Chooser, and System 6 Chooser.
Message-ID: <1991May8.164716.22817@hubcap.clemson.edu>
Date: 8 May 91 16:47:16 GMT
References: <0c9yy7C00WCo4ehFFR@andrew.cmu.edu>
Organization: Clemson University
Lines: 26

From article <0c9yy7C00WCo4ehFFR@andrew.cmu.edu>, by tjh+@ANDREW.CMU.EDU (Tom Holodnik):
> 
> 	What happens when there are lots of System 7 machines and lots of
> System 6 machines, and lots of System 7 file sharing? Device lists under
> System 6 Chooser are more limited (i.e., smaller) than under System 7,
> so there may be some System 6 users who may never see their AppleShare
> server of choice. That is, if there is lots of System 7 filesharing
> going on. 
> 	The folks in our group are currently testing and evaluating System 7.0.
> We've been pondering some transition issues involved in making the
> transition from System 6 to System 7. 
> 	The machines most likely to use System 7 are the machines that are
> memory (and disk) rich, while there may be some population of machines
> that can't make the upgrade, for either economic reasons or for other
> reasons. 
> 	One of the major attractions to System 7 is file sharing. There are
> already a lot of student-run AppleShare servers around. There will be
> even more when System 7 is released with new systems. 
> 	Has anyone else thought of these issues? Does anyone have a plan for
> dealing with this other than to break up their network into smaller
> zones (in which case the number of zones to scan increases, which may be
> another problem for the user).
> 	If anyone has some clever ideas about this, please share them with the list. 
> 
It seems that subneting is a possible solution to this.  But then, if you 
already have too many zones...