Re: Who Owns An Application?
Re: Who Owns An Application?
- Subject: Re: Who Owns An Application?
- From: Matt Deatherage <email@hidden>
- Date: Thu, 22 Jun 2006 04:01:16 -0500
On 6/21/06 at 5:02 PM, Luther Fuller <email@hidden> wrote:
> Is there any way for application B to establish exclusive ownership of
> application A, excluding all user interaction with A, until
> application B is finished, thus protecting data D?
The traditional Macintosh semi-solution to this problem has been file
permissions - not Unix-style permissions, but the fact that if one
program has a file open with write permission, others may not open that
same file with write permission. When you talk about sharing "data,"
it's hard to imagine that you mean in RAM or on the Web, at least for me
(and it is late, so maybe my imagination is just limited right now).
Since 1984, Mac programmers have been advised to keep files open if
they're using the data in them. Once AppleShare came along and volumes
were shared, programmers quickly learned that closing a file meant
someone else might change it. If application "A" is changing data "D",
it should have the file open with write permission, and application "B"
won't be able to access it. Application "B" can then display a warning
that says, "Hey, I need that data, quit Application A until I'm done
munging it."
Not what you want to hear, but canonically, the only way to force a user
to stop using an application is to quit the application - and even then,
the user can relaunch it. It is, as we used to say, his computer.
--Matt (or hers)
--
Matt Deatherage <email@hidden>
GCSF, Incorporated <http://www.macjournals.com>
"Media is the plural of mediocre." -- Jimmy Breslin
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden