Again... the current static nsServiceManager class has been exposed to
external plugin developers for over a year. We do not propose to
promote this depricated interface. However, if this API is frozen (and
being used) we cannot simply remove it.
The public APIs will promote the current methodology for accessing the
service/component manager but for backwards compatability we CANNOT
break existing consumers who are using our "current set of frozen APIs"
-- rick
Mike Shaver wrote:
> Doug Turner wrote:
>
>> Chak Nanga has just posted some of our discussions and proposals on
>> freezing some of the xpcom interface. Please read this document. It
>> contains links to various interface tracking bugs. Please review
>> what we have so far.
>>
>> http://www.mozilla.org/projects/embedding/EmbedInterfaceFreeze.html
>
>
>
> Also, I disagree with the idea of freezing nsServiceManager::* for
> plugin clients. They should get a handle to the service manager
> through some other mechanism, probably a QI of the component manager
> passed in to NSGetModule or nsIModule::getClassObject.
>
> (I ass-u-me that this is the place to discuss these issues.)
>
> Mike
>
