Re: CR: Removal of persistent plugin data

Does the media platform need to be 'restarted' after prefs are deleted, or
perhaps re-initialized? We should make sure we define what state the platform
and engine are in after such a function is called as it can be called at
any time. Perhaps just not allowing the call after some point, not sure.

Personally, I really don't like adding numbers to interfaces as we
have done historically. Sometimes there isn't a better choice, but
in this case I think it might be better named with something that
referes to the platforms persistent data. Then you could clone the
other calls like Purge() and Reset() into this new interface. Perhaps
calls for the PluginPath stuff as well. Might be useful to have an
interface you could pass around that does that kind of stuff but
doesn't have Close(), Init() or other types of calls.

--greg.






Tad Yeager wrote:
> Resending because a portion of a reply wasn't transmitted and there has been only one response.
> 
> Synopsis: encapsulate the removal of persistent plugin data in the MediaPlatform.
> 
> Summary:
> Applications and browser plugins attempt to kill registry keys prior to loading MediaPlatform/ObjectBroker so that plugin handler data will be regenerated when mount points are added.  This happens at installation time or if an application detects that plugins have changed locations. 
> 
> The attached changes to MediaPlatform expose a method that deletes preferences using code factored out of MediaPlatform's Reset() function.  The location and format of the persistent plugin data can change. The attached changes move ownership from MediaPlatform's clients to MediaPlatform.  
> 
> Branchs:
> head, hxclient_3_1_0_atlas
> 
> Affected: 
> MediaPlatform.
> 
> Risks: low.
>