Hello Markus, Thank you for looking into this.
Inga From: Markus Jung [mailto:[email protected]] Sent: Sunday, March 6, 2016 7:35 PM To: Stotland, Inga <inga.stotland at intel.com>; iotivity-dev at lists.iotivity.org Cc: OTC NMG <otc.nmg at intel.com> Subject: Re: [dev] Usage of Iotivity Resource Container APIs Hello Inga, we will fix the issues as soon as possible. I put your issues in https://jira.iotivity.org/browse/IOT-971. Best regards Markus ------- Original Message ------- Sender : Stotland, Inga<inga.stotland at intel.com> Date : Mar 04, 2016 03:58 (GMT+09:00) Title : [dev] Usage of Iotivity Resource Container APIs Hi: Our group is working on developing UPnP/IoTivity bridge using Resource Container APIs. So far, we have encountered a few issues with the exposed APIs. Could anybody please comment on solutions/workarounds? 1. No means to return status from bundle activate/create methods. 2. No means to return status from handleGetAttributesRequest or handleSetAttributesRequest. 3. We can only set one resource type per BundleResource. According to core spec, multiple resource types can be indicated, However, assigning space separated resource type string to m_resource fails in ocstack.c:ValidateResourceTypeInterface. 4. Resource types must be all [a-z][a-z0-9-.]* or URIs (but it looks like the implementation only succeeds under the former). 5. No asynchronous versions of API calls, e.g., calls like handleGetAttributeRequest/handleSetAttributeRequest should provide a version with a callback handler to prevent blocking. Thanks, Inga [Image removed by sender.] -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160307/b5cd4ffb/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: ~WRD000.jpg Type: image/jpeg Size: 823 bytes Desc: ~WRD000.jpg URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160307/b5cd4ffb/attachment.jpg>
