Re: What happens to the AppKit Framework when an user logout ?
Re: What happens to the AppKit Framework when an user logout ?
- Subject: Re: What happens to the AppKit Framework when an user logout ?
- From: Chris Hanson <email@hidden>
- Date: Wed, 17 Oct 2001 17:01:32 -0500
At 11:18 AM -0700 10/16/01, Ali Ozer wrote:
> My current guess is that the AppKit Framework is unloaded during the
logout. Is it correct ?
"unloading" is more of a 9 concept, I think.
"Unloading" is in no way a 9 concept. It's a shared library concept.
Now, AppKit.framework may not be unloaded until nothing using it is
running -- in other words, only when its reference count hits 0 --
but the concept of unloading *is* extremely important in any shared
library system.
For instance, without some sort of real support for unloading, one
can't implement an OpenDoc- or COM-like component architecture.
After all, I should be able to remove an instance of a component from
a document I'm working on, upgrade that component to a new version,
and add a new instance to my document. I realize unloading classes
in Objective-C isn't trivial, but I don't think it's an unsolvable
problem. (It may be in the general case, but specifying restrictions
on classes that can be unloaded shouldn't be too onerous.)
Does NSBundle support unloading in Mac OS X 10.1? I don't recall
seeing anything in the release notes about this, but I'm not on a
10.1 machine right now so I can't check.
-- Chris
--
Chris Hanson <email@hidden>
bDistributed.com: Making business distributed.
Personal email: <email@hidden>