Hello all,

My team is currently interested in consuming the IoTivity APIs and adding new 
functionalities and wrappers on top of it to facilitate its usage for other 
external developers.
We were able to compile IoTivity and have performed some testing using the 
sample applications.
We were also able to compile the simpleServer.cpp and simpleClient.cpp 
application externally for Windows by creating a new SConscript and using the:

-          Headers in iotivity/out/windows/../../include/c_common/,   
iotivity/out/windows/../../include/resource

-          Libs in iotivity/out/windows/../..

-          The boost folder was also needed and copied to 
iotivity/out/windows/../../include/resource/

The table below shows the results obtained for the different platforms using 
the simpleServer and simpleClient applications that are generated when 
compiling IoTivity.

Server

Client

Resources Found

Output message

 Updated and Branch

Android

unsecured Resource

Android

/a/light

Server: Go through the GET request, stops on the PUT request
Client: The GET call goes through
Failed to PUT a light representation for the light resource

Updated 8/1 using the IoTiviy Rel 1.1.1

Android

Secured Resource

Android

/a/light

Server: no additional messages
Client: Resource are found.
Error code UNAUTHORIZED_REQ, request is not authorized by the resource server 
then it stops when the GET call is made

Updated 8/1 using the IoTiviy Rel 1.1.1

Android (unsecure)

unsecured Resource

Windows



Resource found/increased

Updated 8/1 using the IoTiviy Rel 1.1.1

Android

unsecured Resource

Windows



produce error 46

Updated 8/1 using the IoTiviy Rel 1.1.1

Windows

unsecured Resource

Android

N/A

UNAUTHORIZED_REQ

Updated 8/1 using the IoTiviy Rel 1.1.1

Windows

Secured Resource

Android

N/A

Android: no messages
Windows: ALRT 80 invalidate peer
WARN received alert, peer has been invalidated

Updated 8/1 using the IoTiviy Rel 1.1.1

Linux

unsecured Resource

Windows

oic/d, oic/p /a/light

Server: In GET, PUT, POST, GET observe handler
Client: GET request successful
PUT request successful
POST request successful
OBSERVE successful

Updated 09/07/2016
master: d56eaeb9a7805e76f6498da7d66ba5a265e39fa7



Linux

Secured Resource

Windows

oic/d, oic/p /a/light

Server: In GET, PUT, POST, GET observe handler
Client: GET request successful
PUT request successful
POST request successful
OBSERVE successful

Updated 09/07/2016
master: d56eaeb9a7805e76f6498da7d66ba5a265e39fa7

Windows

unsecured Resource

Linux

oic/d, oic/p /a/light

Server: In GET, PUT, POST, GET observe handler
Client: GET request successful
PUT request successful
POST request successful
OBSERVE successful

Updated 09/07/2016
master: d56eaeb9a7805e76f6498da7d66ba5a265e39fa7

Windows

Secured Resource

Linux

oic/d, oic/p /a/light

Server: In GET, PUT, POST, GET observe handler

Client: GET request successful
PUT request successful
POST request successful
OBSERVE successful

Updated 09/07/2016
master: d56eaeb9a7805e76f6498da7d66ba5a265e39fa7

Linux

unsecured Resource

Linux

oic/d, oic/p /a/light

Server: In GET, PUT, POST, GET observe handler
Client: GET request successful
PUT request successful
POST request successful
OBSERVE successful

Updated 09/07/2016
master: d56eaeb9a7805e76f6498da7d66ba5a265e39fa7

Linux

Secured Resource

Linux

oic/d, oic/p /a/light

Server: In GET, PUT, POST, GET observe handler
Client: GET request successful
PUT request successful
POST request successful
OBSERVE successful

Updated 09/07/2016
master: d56eaeb9a7805e76f6498da7d66ba5a265e39fa7


-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160909/ceb7c02d/attachment.html>

Reply via email to