User Tools

Site Tools


infrastructure_of_mpm

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
infrastructure_of_mpm [2017/02/16 11:39]
Tony Mathew [Functionalities supported by MPM]
infrastructure_of_mpm [2017/02/16 12:06] (current)
Tony Mathew [MPMSarr]
Line 33: Line 33:
 </​WRAP>​ </​WRAP>​
  
-===== MPMSarr ​===== +==== MPMSarr ==== 
-  - After loading the plugin, ​Request are made from the client to add, scan, and remove the devices ​of the plugin+  - After plugin ​is loadedrequests can be made from the client to add, scan, and remove the devices. 
-  - This requests are written on the pipe and the request handler takes care of passing the requests to the plugin. +  - These requests(messages from client to plugin) ​are sent over the pipe and the request handler takes care of passing the requests to the plugin. 
-  - The response from the plugins are written over pipe where the mini plugin manager ​accepts different kinds of responses ​from the different plugins and read the response message from the pipe and pass it to the client+  - The response(messages from plugin to client) ​from the plugins are written over the pipethe mini plugin manager ​receives these responses and pass to the sample_client ​
-  - The message ​should be sent from the client which contain a payload and its size. The message should contains the information that client needs to pass to the plugin+  - The request ​message ​consist of message type, size of the payload and payload
-  ​- ​Depending on the request ​from the client to the plugin ​the following four functions are called.+ 
 + 
 +Depending on the request the following four functions are called.
  
 <WRAP center round box 70%> <WRAP center round box 70%>
Line 44: Line 46:
 ===== MPMScan ​ ===== ===== MPMScan ​ =====
  
-  * Initiate the scan request for the particular ​plugin. +  * Initiate the scan request for the plugin. 
-  * Doesn’t need any payload to send to plugin, just a scan request will initiate a scan in the plugin.+  * Doesn’t need any payload to send to plugin.
  
 ===== MPMAdd ​ ===== ===== MPMAdd ​ =====
  
-  * Initiate the add request for the particular ​plugin. +  * Initiate the add request for the plugin. 
-  * Here the payload should contain the data which user will get as a scan response, for instance device Uri.+  * The payload should contain the data (uri of the device), ​which comes in the scan response.
  
 ===== MPMRemove ​ ===== ===== MPMRemove ​ =====
  
-  * Initiate the Remove request for the particular ​plugin. +  * Initiate the Remove request for the plugin. 
-  * Here the payload should contain the data which user will get as a scan response, for instance device Uri+  * The payload should contain the data (uri of the device), ​which comes in the add response. ​
  
  
 ===== MPMReconnect ===== ===== MPMReconnect =====
  
-  * Initiate the Reconnect request ​for the particular plugin.+  * Initiate the Reconnect request.
   * Reconnect metadata and its size should be passed in the reconnect request.   * Reconnect metadata and its size should be passed in the reconnect request.
   * Reconnect happens after the plugin start and it is a one time call.   * Reconnect happens after the plugin start and it is a one time call.
 </​WRAP>​ </​WRAP>​
  
-  * These MPMSARR API’s are not aware of what data is getting ​passed between ​clients to plugin, it just accepts ​the data and pass it to the plugin. +  * The mini_plugin_manager does not process any data passed between plugin ​and client. It just forwards ​the message.
  
  
infrastructure_of_mpm.txt · Last modified: 2017/02/16 12:06 by Tony Mathew