Re: Tracking files the right way
Re: Tracking files the right way
- Subject: Re: Tracking files the right way
- From: Bill Bumgarner <email@hidden>
- Date: Fri, 30 Aug 2002 21:38:58 -0400
On Friday, Aug 30, 2002, at 18:39 US/Eastern, Rosyna wrote:
Keeping this on the topic of cocoa-dev, this is definitely something
that app authors should be very careful of. I would highly recommend
that folks install OS X Server somewhere and compare paths and app
behavior between server and client machines for accounts that use
shared/mounted home directories.
Has Apple released a technote on the difference between server and
client? If so, where? If not, they should ;)
Not that I'm aware of -- it would be a very useful thing. However, it
isn't so much differences between server and client as it is
differences between standalone and network mounted filesystems. It
affects both network mounted user accounts and network mounted
filesystems.
If anything, Apple should document the One True Way (tm) that the
developer should use to reference files in various contexts. I
suspect Apple is distinctly aware of this need and is working towards
this goal, but it-- as a lot of things-- requires a fairly tremendous
amount of design and implementation effort before the OTW can be
advertised at large.
Looking that the evolution of the system (I believe 4k19 was one of the
earliest OS X builds *I* got to play with), many, many aspects of
filesystem management and reference have been vastly improved....
... but we still have a long way to go.
If your app does not work on non-HFS+ filesystems, make sure you at
least detect this situation and give the user a useful error message
(as opposed to the completely random behavior exhibited by many apps
now).
I completely agree, but it's hard to say it won't work on UFS if it's
never tested. It may work just jim dandy. It might not work at all. If
it works fine, why scare the user?
Then test it!
At least, test against iDisk given that Apple is pushing ".mac" as a
major part of the OS X user experience. Better yet, rebuild your
machine with a small UFS partition and drag your app there and work
with documents saved on said partition -- not only will it exercise
your app in a UFS context, it'll also exercise your app in a context
fairly close to working with the app on an NFS or Samba/Windows mount
point.
My original statement was not advocating warning the user when no known
problem exists -- but to warn the user when they are working with a
filesystem with which your app is not compatible...
b.bum
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.