Newsgroups: comp.protocols.appletalk
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!snorkelwacker.mit.edu!ira.uka.de!smurf!urlichs
From: urlichs@smurf.sub.org (Matthias Urlichs)
Subject: Re: AppleShare Volume Limits
Message-ID: <B!G-W1C@smurf.sub.org>
Date: Sun, 16 Jun 1991 21:35:47    
Organization: University of Karlsruhe, FRG
References: <3C67F76744400065@BITNET.CC.CMU.EDU>
Lines: 23

In comp.protocols.appletalk, article <3C67F76744400065@BITNET.CC.CMU.EDU>,
  MCMAHON@GRIN1.Bitnet ("McMahon,Brian D") writes:
<  
< Ken Wallewein <kenw@NOAH.ARC.AB.CA> writes:
< >  Some one told me that, in AFP, there is a theoretical maximum number of
< >volumes which can be "published" by a given AppleShare server, and that
< >that number is actually quite low.
<  
<  
< Again, any clues about what in blazes is going on here would be welcome ...
< and just might preserve my few remaining tattered shreds of sanity.  :-)

The problem is the list of volumes the server sends back to the client.
If the client wants a one-block ATP response (and I think AppleShare does it
that way), that list has to fit in 572 bytes.

< It sure as Hell isn't in any Apple docs I've seen.

Sometimes that stuff has to be intuited. :-(

-- 
Matthias Urlichs -- urlichs@smurf.sub.org -- urlichs@smurf.ira.uka.de     /(o\
Humboldtstrasse 7 - 7500 Karlsruhe 1 - FRG -- +49-721-621127(0700-2330)   \o)/
