I'm in favor of not adding anything new to the server. But yes GET /oic/d is better. Or even a regular ping (i.e., ICMP echo request).
-----Original Message----- From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of Thiago Macieira Sent: Wednesday, July 5, 2017 5:30 PM To: iotivity-dev at lists.iotivity.org Subject: Re: [dev] New Request Type: PING (Like Get, Put, Post, ...) On quarta-feira, 5 de julho de 2017 10:22:57 PDT Dave Thaler via iotivity-dev wrote: > How is that different from a unicast GET /oic/res? There's a non-negligible action on the device to respond to that request. I would recommend getting /oic/d instead, unless we can come up with an item that is even less CPU-intensive. How about a CoAP HEAD request instead of GET? -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ iotivity-dev mailing list iotivity-dev at lists.iotivity.org https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.iotivity.org%2Fmailman%2Flistinfo%2Fiotivity-dev&data=02%7C01%7Cdthaler%40microsoft.com%7Cea598986b76b4e2feec708d4c4063030%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636348978246404073&sdata=boLjLlFDXUDtnQdVIlc2I2Z0KzgtHyiwEx7ucU2y04A%3D&reserved=0
