User Tools

Site Tools


requirements_of_a_plugin

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
requirements_of_a_plugin [2017/07/01 20:11]
Joseph Morrow
requirements_of_a_plugin [2017/07/01 20:12] (current)
Joseph Morrow
Line 14: Line 14:
   * [S] Make proper usage of Plugin Interface API pluginRemove() \\delete or make an IoTivity resource inactive. If adhering to pluginReconnect(),​ must delete IoTivity resource endpoint data from your.   * [S] Make proper usage of Plugin Interface API pluginRemove() \\delete or make an IoTivity resource inactive. If adhering to pluginReconnect(),​ must delete IoTivity resource endpoint data from your.
  
-  * [O] Make proper usage of Plugin Interface API pluginReconnect() \\In pluginAdd, you can optionally decide to track  your proprietary plugin'​s endpoint data and IoTivity resource endpoint data and serialize it into a byteArray. This byteArray is returned to pluginReconnect() to allow this plugin to reconnect without user intervention in case of a power cycle. This byteArray can be in any format or size you'd like. It is your plugin'​ context per device.+  * [O] Make proper usage of Plugin Interface API pluginReconnect() \\In pluginAdd, you can optionally decide to track  your proprietary plugin'​s endpoint data and IoTivity resource endpoint data and serialize it into a byteArray. This byteArray is returned to pluginReconnect() to allow this plugin to reconnect without user intervention in case of a power cycle. This byteArray can be in any format or size you'd like. It is your plugin'​ context per device. Your plugin must simply know how to pack and parse it. No other layer needs to understand it outside of a byteArray of some size.
requirements_of_a_plugin.txt ยท Last modified: 2017/07/01 20:12 by Joseph Morrow