Re: a proposal for 2 OAF features



On 5 Jul 2000, Maciej Stachowiak wrote:

> Is is possible that OAF would later try to activate other objects
> (either private or non-private) from the same running executable? If
> so, the exclusive_iid variable may need to be a list, and perhaps
> should apply only to the first activation of a given IID?

Hmm, thinking about this some more, the thing is that if a private object
is activated via an executable, then there is really no chance if any
activations from other process returning objects in that process, and
shared library activations (which will be in that process) are implicitly
"private" anyways.

We need to get a list of use cases to find out how this private thing is
supposed to work. There are some issues (such as "what if an executable
creates & registers multiple objects upon startup, irrelevant of whether
it was activated for a private object") that could cause problems.

-- Elliot
The best way to accelerate a Macintosh is at 9.8 meters per second per second.





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]