Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!sdd.hp.com!uakari.primate.wisc.edu!crdgw1!uunet!intercon!news
From: kdb@macaw.intercon.com (Kurt Baumann)
Newsgroups: comp.protocols.appletalk
Subject: Re: MacNFS vs AppleShare
Message-ID: <274864DC.19E7@intercon.com>
Date: 19 Nov 90 23:03:55 GMT
References: <4665@husc6.harvard.edu> <1990Nov10.100943.1166@urz.unibas.ch> <273EDDB5.40D1@intercon.com> <1990Nov13.091518.1171@urz.unibas.ch> <274043EF.4F0E@intercon.com> <9160@ncar.ucar.edu> <27430546.6B52@intercon.com> <1990Nov16.155133.15932@ux1.cso.uiuc.edu>
Sender: usenet@intercon.com (USENET The Magnificent)
Reply-To: kdb@macaw.intercon.com (Kurt Baumann)
Organization: InterCon Systems Corporation, Herndon, VA
Lines: 45

In article <1990Nov16.155133.15932@ux1.cso.uiuc.edu>,
dorner@pequod.cso.uiuc.edu (Steve Dorner) writes:
> In article <27430546.6B52@intercon.com> kdb@macaw.intercon.com (Kurt Baumann) writes:
> >Yes.  Both can be changed in an AppleSingle file.
> 
> With GREAT pain and suffering, right?  Don't you have to rewrite practically
> the entire file in the worst case?  So the entire file has to traverse
> the network twice (or does the NFS protocol allow you to tell the server to do
> some things locally?).
> 
> AppleSingle is an icky way to run a filesystem, unless you KNOW you will only
> be playing with one fork, or so it seems to me.
> 

We handle this algorithmically (much as it is done in Apple A/UX).  We do
this in order to cut down on the clutter on the UNIX side and in order to
be compatible with A/UX built file systems.  This way you can use the same
file system from either A/UX or MacOS with NFS/Share.

> >> If so, how do you decide when to do the translation?
> >Yes, if it is a Macintosh text file we translate CR-to-LF when output and
> >reverse on input.  The UNIX text files are also treated this way.
> 
> Uh, how do you decide if a UNIX file is a text file?  Or a mac file for that
> matter; there are some applications that create text files that have creators
> other than 'TEXT' (TeachText comes to mind)?

On the UNIX side we determine by the contents of the file (and this does
not make it slow).  On the Mac it is determined by a list of types that we 
consider to be text.

> Now, for my own question: Does your product work with MacTCP?  If it
> does, I may be a customer.  If it doesn't, I have suddenly lost interest...
> --

Yes, until something better comes along we will support MacTCP, and even
after that.

> Steve Dorner, U of Illinois Computing Services Office
> Internet: s-dorner@uiuc.edu  UUCP: uunet!uiucuxc!uiuc.edu!s-dorner

--
Kurt Baumann                       InterCon Systems Corporation
703.709.9890                      Creators of fine TCP/IP products
703.709.9896 FAX               for the Macintosh.