You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 18, 2017. It is now read-only.
PluginHandler should support resolving an active protocol for registered IPlugins. This also involves updating the IPlugin signature to contain protocol based information for the PluginHandler to use/set.
The text was updated successfully, but these errors were encountered:
- When a plugin is registered with the system a client protocol can now be provided. This protocol is then cross checked with the created IPlugin's protocol and the result of Register returns the Protocol that will be used when communicating with the registered Plugin.
- Added tests to validate error conditions and protocol resolutions.
#1905
- When a plugin is registered with the system a client protocol can now be provided. This protocol is then cross checked with the created IPlugin's protocol and the result of Register returns the Protocol that will be used when communicating with the registered Plugin.
- Added tests to validate error conditions and protocol resolutions.
#1905
- Removed PluginProtocolMessage because it's now handled by the PluginHandler in the DTH.
- Updated ProcessMessage to match the new IPlugin contract. This included indicating if a message was handled or not via the return message.
- Removed PluginProtocolMessage tests.
- Added handled checking to existing tests.
- When a plugin is registered with the system a client protocol can now be provided. This protocol is then cross checked with the created IPlugin's protocol and the result of Register returns the Protocol that will be used when communicating with the registered Plugin.
- Added tests to validate error conditions and protocol resolutions.
#1905
PluginHandler
should support resolving an active protocol for registeredIPlugin
s. This also involves updating theIPlugin
signature to contain protocol based information for thePluginHandler
to use/set.The text was updated successfully, but these errors were encountered: