Path: utzoo!attcan!uunet!wuarchive!uwm.edu!mailrus!ames!uhccux!munnari.oz.au!cs.mu.oz.au!kre
From: kre@cs.mu.oz.au (Robert Elz)
Newsgroups: comp.protocols.appletalk
Subject: Re: Speeding CAP file access for EtherTalk Macs.
Message-ID: <2588@munnari.oz.au>
Date: 30 Oct 89 10:19:43 GMT
References: <8910300211.AA16825@cuba.Cayman.COM>
Sender: news@cs.mu.oz.au
Lines: 21

In article <8910300211.AA16825@cuba.Cayman.COM>, brad@cayman.com writes:
> The bottom line is that CAP will speak to one and only one "gateway".

This is true, and it means that to use CAP you must have
a real  (IPtalk capable) appletalk router on your net.
That is, regardless of whether all your macs are on ethernet
and speak IPtalk directly.

However, this does not really affect performance, its not necessary
for all packets to go throgh the gateway .. CAP remembers where it
received its last packet from, and if the next one that it has to
send is going to that appletalk address, it sends it to the
associated IP address.  This is basically every packet that most of
the standard CAP applications send (they're servers, the first
packet comes from the mac client, the server just replies).  The
exception is lwsrv (which initiates the connection to the laserwriter)
but since you're unlilely to be putting an IPtalk driver in your
laserwriter, this is irrelevant (and in any case, its only the NBP lookup,
and then the first packet that has to go through the gateway).

kre