Path: utzoo!attcan!uunet!husc6!cmcl2!brl-adm!umd5!purdue!decwrl!ucbvax!noah.arc.CDN!kenw
From: kenw@noah.arc.CDN (Ken Wallewein)
Newsgroups: comp.protocols.appletalk
Subject: KIP/CAP, Kinetics comparison
Message-ID: <1680*kenw@noah.arc.cdn>
Date: 29 May 88 02:24:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 21


  Would somebody _please_ summarize the differences between KIP/CAP and 
Kinetics software for the Fastpaths? 

  As I understand it, CAP is actually Unix-based Appletalk, Appleshare, and 
print spooling software. It's unclear to me whether CAP can talk Ethertalk, or 
must have a Fastpath to be useful.

  KIP, on the other hand, is (I believe) software for the Fastpath, which 
requires communication with a CAP machine to function properly. I don't 
believe it supports Ethertalk gatewaying. As I understand it, KIP talks to CAP 
via Appletalk encapsulated in TCP/IP.

  Kinetics software for the Fastpath is reputedly somewhat less capable, but 
apparently supports both Ethertalk and IP routing. 

  If I want to use Pacer-based Appleshare on our VAX/VMS machine, and CAP-
based Appleshare on a Sun, I guess I gotta use Kinetics' etalk-gw.srec, 
right?

/kenw