Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.csd.uwm.edu!cs.utexas.edu!uunet!intercon!amanda@intercon.uu.net
From: amanda@intercon.uu.net (Amanda Walker)
Newsgroups: comp.sys.mac.programmer
Subject: Re: System 7.0
Message-ID: <1394@intercon.UUCP>
Date: 23 Aug 89 21:50:15 GMT
References: <227700026@uxa.cso.uiuc.edu> <483@sunfs3.camex.uucp> <9173@thorin.cs.unc.edu> <13784@shamash.cdc.com> <490@sunfs3.camex.uucp> <8368@hoptoad.uucp> <3214@zeus.unl.edu>
Sender: news@intercon.UUCP
Reply-To: amanda@intercon.uu.net (Amanda Walker)
Organization: InterCon Systems Corporation
Lines: 26

In article <3214@zeus.unl.edu>, unocc07@zeus.unl.edu (Dave Caplinger) writes:
> In article <8368@hoptoad.uucp>, tim@hoptoad.uucp (Tim Maroney) writes:
> > On a semi-related note, what is this file id crap?  How are network
> > file system implementors supposed to implement yet another
> > Mac-file-system-only feature on servers on other operating systems?
> 
> Isn't the file-id information just taken straight out of AppleShare?
> (the new format for the Desktop file(s))  If so, it's not really "yet
> another" different thing in the Mac file system.

AppleShare & the new desktop interface don't use file IDs; it's something
new, and something which I think can only encourage bad programming...

As for Tim's note, I'm afraid the people working on the Mac file system
simply don't care.  It fits into Apple's general attitude towards other
machines doing things that "could be done with Macs": "Why would you want
to do that?"  They even take this stand towards some of their own products,
annoyingly enough :-(.

Grumble.

--
Amanda Walker
InterCon Systems Corporation

amanda@intercon.uu.net    |    ...!uunet!intercon!amanda