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
The notion of "base" plugins should be documented, where a "base" plugin is a layer of abstraction on top of the SDK which may provide a base for a given class of plugins. This base can provide common utility functions, protocol handling, etc, and may define easier ways for "subclassed" plugins define devices / handlers / etc.
A good example of this is with the work around generalizing the SNMP plugin, where the "base" provides handling for the SNMP protocol handling and device config management, and "subclassed" plugins only need to define devices for their MIB(s).
The text was updated successfully, but these errors were encountered:
The notion of "base" plugins should be documented, where a "base" plugin is a layer of abstraction on top of the SDK which may provide a base for a given class of plugins. This base can provide common utility functions, protocol handling, etc, and may define easier ways for "subclassed" plugins define devices / handlers / etc.
A good example of this is with the work around generalizing the SNMP plugin, where the "base" provides handling for the SNMP protocol handling and device config management, and "subclassed" plugins only need to define devices for their MIB(s).
The text was updated successfully, but these errors were encountered: