[Adium-devl] Out of process plugins (was: Distant objects)

[Augie Fackler]

On May 8, 2007, at 8:24 AM, Evan Schoenberg wrote:

>> I say do it, and force all plugins out of process. It'll be a win for
>> us in terms of forcing people not to use private APIs and keeping
>> plugins from crashing Adium. Although I can be convinced otherwise ;)
> Disagree there.  DO is inherently more expensive than in-process.   
> A rich public API should hopefully keep people from doing dumb  
> things like NSClassFromString() to hack into private classes... and  
> if they do, well, our handling of plugins should be versioned such  
> that this isn't a major problem anyways: if I write a plugin  
> depending on 1.0.2's internals, and say it's compatible with the  
> 1.0.2 API only, then with 1.0.3 the user should be warned of the  
> potential incompatibility and reminded how to manually remove the  
> plugin if necessary.

We could always start actually having a policy about when it's OK to  
remove calls off of publicly accessible objects...this is something  
we probably should have been doing for a while anyway.
Is there any interest in this?

Augie

>
> -Evan