Once later HTTPS add-on does not affect the CA layer architecture, incremental release is valid. -----Original Message----- From: Thiago Macieira [mailto:thiago.macie...@intel.com] Sent: Friday, July 29, 2016 1:47 PM To: ???(Uze Choi) Cc: ashok.channa at samsung.com; iotivity-dev at lists.iotivity.org Subject: Re: [dev] CoAP - HTTP Proxy Review Request
On sexta-feira, 29 de julho de 2016 13:05:42 PDT ???(Uze Choi) wrote: > Regarding your comment : > "most of the changes to the CA layer that make it work with HTTP > become superfluous and should not be applied." -> CA layer affect > thinDevice-G/W side not for G/W-WebServer(HTTP/HTTPS). That's not the change that I saw. It was modifying the CA layer in order to implement the HTTP socket. I'm saying that if we use a third-party library, none of those changes will be necessary. > We can release the HTTPS code for G/W-WebServer incrementally. > At least, HTTPS does not affect the thinDevice-G/W path implementation. Right. So long as HTTPS is there on the first IoTivity release. I'm not backing down from this: HTTPS support is mandatory. Until then, keep it in a branch, not in master. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
