Hello Uze, thanks for your thoughts. We considered and liked your suggestion. I?ll move IPCA to Resource directory. Thanks!
From: ??? [mailto:[email protected]] Sent: Wednesday, March 8, 2017 11:18 PM To: Soemin Tjong <stjong at exchange.microsoft.com>; Thiago Macieira <thiago.macieira at intel.com>; Thiago Moura <thiagogcm at gmail.com> Cc: iotivity-dev at lists.iotivity.org Subject: RE: RE: IPCA Currently resource encapsulation is a scope of service and in the service directory but this looks more appropriate to be located at resource directory. Service is more suitable to additional resource data model or protocol on top of base layer. Regarding directory I cannot imagine how cloud and other services can be integrated as of now with current design. So I'm skeptical to be in api or sdk directory. BR Uze Choi --------- Original Message --------- Sender : Soemin Tjong <stjong at exchange.microsoft.com<mailto:stjong at exchange.microsoft.com>> Date : 2017-03-08 19:19 (GMT+1) Title : RE: IPCA Service as additional features on top of the IoTivity stack is my understanding too. Background discovery, presence monitoring and tracking of outstanding requests are what IPCA does currently building on the IoTivity stack. I realize there?s some overlap with resource broker and resource encapsulation C++ APIs in the Service. Internally IPCA reconstructs and caches the device information (based on resources on device). This is useful when the server?s URI has changed (e.g., when device restarts and the IoTivity stack comes back up with new ephemeral UDP/TCP ports). Now, IPCA does not cache resource data at this time, I suppose until there?s a need to do that (like when it runs as a daemon service for multiple apps, the IPCAOpen() API called by each app is for that purpose). Additional features building on the IoTivity stack (like seamless Cloud integration, monitoring of new resources and working with IoTivity bridges) may be added later. One thought is if a new ?sdk? (or ?api?) directory at root would make sense as we formalize the API design going forward. Thanks From: ??? [mailto:[email protected]] Sent: Wednesday, March 8, 2017 2:02 AM To: Soemin Tjong <stjong at exchange.microsoft.com<mailto:stjong at exchange.microsoft.com>>; Thiago Macieira <thiago.macieira at intel.com<mailto:thiago.macieira at intel.com>>; Thiago Moura <thiagogcm at gmail.com<mailto:thiagogcm at gmail.com>> Cc: iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: RE: IPCA Primitive service aims to provide a specific feature on top of base layer. Accoring to your comment there is few additional value as a service I feel. It look just a different style of base layer API, even though you mention discovery running in background but does not look enough as a separate service. I could be wrong then please give your opinion. BR Uze Choi --------- Original Message --------- Sender : Soemin Tjong <stjong at exchange.microsoft.com<mailto:stjong at exchange.microsoft.com>> Date : 2017-03-08 10:09 (GMT+1) Title : IPCA Agreed, I created Jira: https://jira.iotivity.org/browse/IOT-1904 and a wiki page for IPCA: https://wiki.iotivity.org/ipca. The proposal is for a set of higher level C APIs for application developers as well as code generation tools building on the C++ & ocstack?s C APIs (that are too low level with many functionalities supported by a method like OCDoRequest()). To reduce the complexity for apps and generated code, IPCA also performs functions like periodic discovery in the background, timing out outstanding requests that didn?t get responses and detecting server down while there?s an outstanding observe on its resource. The proposal is to create IPCA directory in Service directory. Thanks Soemin From: ??? [mailto:[email protected]] Sent: Tuesday, March 7, 2017 10:42 PM To: Soemin Tjong <stjong at exchange.microsoft.com<mailto:stjong at exchange.microsoft.com>>; Thiago Macieira <thiago.macieira at intel.com<mailto:thiago.macieira at intel.com>>; Thiago Moura <thiagogcm at gmail.com<mailto:thiagogcm at gmail.com>> Cc: iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: RE: Re: [dev] API Review function Great. Wiki for this feature could be first step which we can communicate. BR Uze Choi. --------- Original Message --------- Sender : Soemin Tjong <stjong at exchange.microsoft.com<mailto:stjong at exchange.microsoft.com>> Date : 2017-03-08 01:13 (GMT+1) Title : Re: [dev] API Review function Sorry for getting to this thread late. Regarding other platforms, I'm almost there getting IPCA to build for Linux. I'll also create a Jira and Wiki for IPCA. Soemin -----Original Message----- From: iotivity-dev-bounces at lists.iotivity.org<mailto:iotivity-dev-bounces at lists.iotivity.org> [mailto:[email protected]] On Behalf Of Thiago Macieira Sent: Thursday, March 2, 2017 8:34 PM To: Thiago Moura <thiagogcm at gmail.com<mailto:thiagogcm at gmail.com>> Cc: iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: Re: [dev] API Review function Em quinta-feira, 2 de mar?o de 2017, ?s 20:17:35 PST, Thiago Moura escreveu: > Hi Uze, > Talking about IPCA.. I noticed the "initial commit" this week on > master branch, but there was no word about this feature over here. > Where does this kind of feature discussion happens? And why IPCA only targets > Windows? That commit is the beginning of the discussion. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ iotivity-dev mailing list iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> https://lists.iotivity.org/mailman/listinfo/iotivity-dev _______________________________________________ iotivity-dev mailing list iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> https://lists.iotivity.org/mailman/listinfo/iotivity-dev [cid:image001.gif at 01D299E7.1323BCD0] [http://ext.samsung.net/mail/ext/v1/external/status/update?userid=uzchoi&do=bWFpbElEPTIwMTcwMzA5MDcxODIwZXBjbXMxcDZhM2U5MTBhMzA4YjExMWViNGIwZWUxN2UzNjlhNTI5NyZyZWNpcGllbnRBZGRyZXNzPXN0am9uZ0BleGNoYW5nZS5taWNyb3NvZnQuY29t] -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170311/fc58aef9/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 13402 bytes Desc: image001.gif URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170311/fc58aef9/attachment.gif>
