Path: utzoo!attcan!uunet!dino!ux1.cso.uiuc.edu!pequod.cso.uiuc.edu!dorner
From: dorner@pequod.cso.uiuc.edu (Steve Dorner)
Newsgroups: comp.protocols.appletalk
Subject: Re: MacNFS vs AppleShare
Message-ID: <1990Nov16.155133.15932@ux1.cso.uiuc.edu>
Date: 16 Nov 90 15:51:33 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>
Sender: news@ux1.cso.uiuc.edu (News)
Reply-To: dorner@pequod.cso.uiuc.edu (Steve Dorner)
Organization: University of Illinois at Urbana-Champaign
Lines: 24

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.

>> 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)?

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...
--
Steve Dorner, U of Illinois Computing Services Office
Internet: s-dorner@uiuc.edu  UUCP: uunet!uiucuxc!uiuc.edu!s-dorner