A necessary but not sufficient guideline for meeting Thiago's requirement is that TCP be treated as an adapter separate from IP. The current IP Adapter might better be named the UDP adapter. A separate TCP adapter would fit both the spirit and de facto design of the connectivity layer.
John Light Intel OTC OIC Development -----Original Message----- From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of Thiago Macieira Sent: Wednesday, August 19, 2015 12:20 AM To: iotivity-dev at lists.iotivity.org Subject: [dev] TCP must be optional Hello all I'm seeing a few changes go about CoAP over TCP and I'm wondering what those are for. Please make sure that TCP support remains forever optional in IoTivity. No device should be required to have it, as we'll have both networks and operating systems that lack TCP support. That means no feature can depend on TCP and must work over UDP (unless the feature itself is optional). Any TCP support must be negotiated after getting the capabilities of both end-points as well as any intermediaries along the way. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
