Re: Busy Status
Re: Busy Status
- Subject: Re: Busy Status
- From: John W Baxter <email@hidden>
- Date: Sun, 3 Nov 2002 10:16:20 -0800
At 23:33 -0500 11/2/2002, Rob Jorgensen wrote:
>
>OSX changes the way files are shared. No longer does have having a
>
>file open for write access prevent another process from opening it
>
>for write access, which prevents this command from working. I'm
>
>looking into what it would take to fix this, but I haven't found
>
>anything worth implementing yet, and if I don't, I'll probably just
>
>remove the command.
>
>
Thanks for confirming this seemingly hazardous situation. Just today
>
I noticed that a script could write to a file that was already open
>
in TextEdit but I didn't push it to see what would happen if I edited
>
and saved the file with TE while the script was writing. It seems
>
that no good could come from it and I wonder how to prevent problems
>
in the rare cases where this might occur.
Unix uses file "locking" done "voluntarily" by the applications involved.
In fact, several locking mechanisms are used, none of them wholly
satisfactory (particularly when application "A" uses one mechanism and
application "B" uses another).
It's a jungle out there.
--John
--
John Baxter email@hidden Port Ludlow, WA, USA
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.