Hi Venu, What sample client are you using?
Also, what version of IoTivity are you using? If using Git, a commit id should suffice. If not, a version number and specifying the source you received it from should suffice too. If you?re using the iotivityandzigbeeclient, it has/had a bug in IoTivity 1.2.1 I just learned of last week. It has a single OCDevAddr struct for the entire application. Where in reality it should have an OCDevAddr struct for each resource discovered. The effect is that the iotivityandzigbeeclient application points all requests to the server associated with the last resource found. Here?s a changeset: https://gerrit.iotivity.org/gerrit/#/c/21263/ If it isn?t merged quickly by IoTivity community, you can pull it down as a patch or make the changes manually in your local copy. Thanks, Joey Morrow From: <iotivity-dev-bounces at lists.iotivity.org<mailto:iotivity-dev-bounces at lists.iotivity.org>> on behalf of venu krishnamurthy via iotivity-dev <iotivity-dev at lists.iotivity.org<mailto:[email protected]>> Reply-To: venu krishnamurthy <venubk_77 at yahoo.com<mailto:venubk_77 at yahoo.com>> Date: Tuesday, July 4, 2017 at 1:32 AM To: "iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org>" <iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org>> Subject: [dev] handling 2 plugins together. Hi All, I am venuB K. I am studying Iotivity bridging. Gone through all sample applications. and built my own plugins, STUB1 and STUB2. tested them individually it is working fine. when i added both plugins. client side i am able to see uri's corresponding to both plugins. but when i send request only one plugin is responding either STUB1 or STUB2. my question is. whether i need to open 2 clients to communicate to each plugins. OR one client to enough to serve the purpose. if this is true what change i need to do in server side to handle both requests. Thanks and regards. Venu -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170706/e18f4126/attachment.html>
