Re: Exclusive File Access
Re: Exclusive File Access
- Subject: Re: Exclusive File Access
- From: Ondra Cada <email@hidden>
- Date: Thu, 21 Nov 2002 00:29:45 +0100
On Wednesday, Nov 20, 2002, at 23:25 Europe/Prague, Rosyna wrote:
Doesn't help recover the last 2 hours of work you did because some
editor (person) decided to open your project file, changed a saved
selection, and saved it back to disk.
Just Save As to another file. Or just Save -- rewriting so *his* work,
of course.
Of course I am thinking of 100+ megabyte photoshop files being served
off a server via gigabit.
I'm not sure you would edit 100+ MB picture in-RAM. If so, I'd say,
poor you and poor Photoshop...
It'd be best to issue a warning *before* you start editing, not after.
It's not possible. The other person might open the file later, and he
might want just to peek into it without changing. Or you might want
*not* to save the file to the original location, which means there's no
conflict again. The first moment a conflict occurs is, as I've said,
when anyone tries to save and the file is no more the one he has read
in.
Well of course you might check when file changes and issue immediately
a warning "someone just changed a file under your foot, do you want (a)
load it losing your changes, (b) overwrite it losing his changes, (c)
Save As becoming independent"; you can even keep track of changes and
do it even more sophisticately... but, at the very least for the *VAST*
majority of applications where a simultaneous access to data is an
exception, it would be a vast overkill, or, in other words,
*completely* wasted effort which otherwise could be used for
*infintely* more important features.
---
Ondra Cada
OCSoftware: email@hidden
http://www.ocs.cz
private email@hidden
http://www.ocs.cz/oc
_______________________________________________
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.