Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ncar!tank!uwvax!puff!cat24!koehn
From: koehn@cat24.CS.WISC.EDU (Bradley Koehn)
Newsgroups: comp.protocols.appletalk
Subject: Re: the comming appletalk crisis
Keywords: AppleTalk, traffic
Message-ID: <2306@puff.cs.wisc.edu>
Date: 22 Feb 89 20:22:25 GMT
References: <514@nanovx.UUCP> <1959@helios.ee.lbl.gov>
Sender: news@puff.cs.wisc.edu
Reply-To: koehn@cat24.CS.WISC.EDU (Bradley Koehn)
Organization: U of Wisconsin CS Dept
Lines: 13

I have what may or may not be a relief to the problem, if not
a solution.  Why not run Appletalk through both serial ports?  This way, you
could dedicate one port to exclusive local traffic (printing, file servers,
etc.), anduse the other for global traffic (global servers, company-wide
email, etc.)?  I realize this would not solve the node-limit problem, but
it could significantly reduce traffic without the overhead of bridges, and
still remain compatible with current Appletalk equiptment.

Brad Koehn, U of W Madison

"Fly like an Emu!"

DISCLAIMER: My thoughts and opinions are just that. Mine.