RE: CR: removing persistent plugin data withMediaPlatform

- We can't add a new method to an existing interface. This violates the COM
policy. IHXMediaPlatform is a relatively new interface, however, there maybe
other Helix community products/projects using this interface already. We
need to create a new interface(IHXMediaPlatform2) for this new method.
 
- Not directly relate to your changes, is there reason why we keep a private
interface(IRMAMediaPlatform) which is idential(same GUID & methods) to the
public version(IHXMediaPlatform)? Can't we switch to Helix interface to
minimize maintenace down the road?
 
Henry

  _____  

From: [email protected]
[mailto:[email protected]] On Behalf Of Tad Yeager
Sent: Thursday, February 19, 2009 5:55 PM
To: [email protected]
Subject: [Helix-client-dev] CR: removing persistent plugin data
withMediaPlatform



Synopsis: encapsulate the

removal of persistent plugin data in the MediaPlatform.



Summary:
Applications (eg realplayer) and browser plugins (eg rpbrowserecordplugin)
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. 

MediaPlatform owns a Plugin2Handler which attempts to rewrite the plugin
handler data if persistent checksums don't match when AddPluginMountPoint is
called.  However,  Plugin2Handler::ReloadPluginsNoPropagate can do a partial
regeneration, rewriting FileInfo but not PluginInfo for the dlls in
FileInfo.  This happens when the plugin handler data store's checksum fails
(ReadPluginInfoFast) but the dll checksum does not fail in
ReloadPluginsNoPropagate. 

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 ObjectBroker/MediaPlatform's clients to
MediaPlatform.  



Branch:

head, hxclient_3_1_0_atlas



Affected:

Media Platform.



Risks:

low.



Please review the attached diffs.  Let me know if you have questions

or suggestions.

_______________________________________________
Helix-client-dev mailing list
[email protected]
http://lists.helixcommunity.org/mailman/listinfo/helix-client-dev