Added API to obtain OCResourceObject from RCSRemoteResourceObject.
authorAbhishek Pandey <abhi.siso@samsung.com>
Thu, 21 Jul 2016 10:31:23 +0000 (16:01 +0530)
committerAshok Babu Channa <ashok.channa@samsung.com>
Thu, 4 Aug 2016 05:01:53 +0000 (05:01 +0000)
commit29cd11df2014407af9de2335e0aad25d89717f58
tree160c3a6600f784b05d1f9d91564ac9d7ceab0baf
parente599b887acbfffa61e0ce5ba928ad6540b099a37
Added API to obtain OCResourceObject from RCSRemoteResourceObject.

Resource Encapsulation layer's RCSRemoteResourceObject class does not provide
all the operations (e.g. PUT, DELETE) that IoTivity base layer provides.

If application wants to invoke base layer API's directly, it needs to obtain
OCResoureObject. Obtaining this object is not possible without calling base
layer discovery. However, if application wants to use both RE layer and Base
layer there will be redundant discovery going on.

To avoid this problem, we added an API that returns OCResoureObject maintained
in RE layer. Using this object, application can call base layer APIs without
additional discovery.

Change-Id: I87757d70bd5df3463c3573831d7392e7b45c670a
Signed-off-by: Abhishek Pandey <abhi.siso@samsung.com>
Reviewed-on: https://gerrit.iotivity.org/gerrit/9551
Tested-by: jenkins-iotivity <jenkins-iotivity@opendaylight.org>
Reviewed-by: Hun-je Yeon <hunje.yeon@samsung.com>
Reviewed-by: Jay Sharma <jay.sharma@samsung.com>
Reviewed-by: Junghyun Oh <junghyun.oh@samsung.com>
Reviewed-by: Ashok Babu Channa <ashok.channa@samsung.com>
service/resource-encapsulation/include/RCSRemoteResourceObject.h
service/resource-encapsulation/src/resourceClient/RCSRemoteResourceObject.cpp
service/resource-encapsulation/unittests/ResourceClientTest.cpp