According register()API in the OCF Server API, the secure property seems similar to the OC_SECURE flag in IoTivity C API for selecting coaps:// as the connection protocol. However, after registering a resource with secure: true property, the client still get coap:// endpoint address of that resource during the discovery.
According
register()
API in the OCF Server API, thesecure
property seems similar to theOC_SECURE
flag in IoTivity C API for selectingcoaps://
as the connection protocol. However, after registering a resource withsecure: true
property, the client still getcoap://
endpoint address of that resource during the discovery.