?and that is exactly what you would want for the http, isn?t it? So by generalizing this existing mechanism (to cover http too) you could not only tackle this use case: a proxy exposing resources from coap(s) through http(s) but also existing OCF use cases an OCF device exposing its resources directly through multiple endpoints, including http(s) and so keep everything secured under the same flag.
From: ???? [mailto:dwarka.day...@samsung.com] Sent: Friday, 29 July, 2016 1:09 PM To: Stephane Lejeune (stlejeun); ???; 'Thiago Macieira'; ?? Cc: iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org>; ???? Subject: RE: Re: [dev] FW: Re: Re: CoAP - HTTP Proxy Review Request SECURED flag does not build unsecured resource but allows the resource to be accessed through COAP due to wild-card. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160729/92b3c27e/attachment.html>
