On 07/23/2018 03:29 AM, Ravee wrote: > Hi, > > Looks like, I found a bug in observer code. I used CPP SDK for my > application. > > When the client(observer), goes away without notifying the server, the > server still tries to send notifications. Since, the client is not longer > available, the server receives communication failures and removes the > observer from the list
that part is all in accordance with RFC 7641, upon which the OCF observe spec, and the iotivity implementation, are based. > Since the Resource and Request Handles are NULL in OCStackFeedBack, the > application entity handler is never called. This results, in holding an > invalid observer ID by the application. Any future observations sent by > the Server, results in crashing the Server, as the observer ID held by the > application is invalid. that's not so cool. Could you file a ticket explaining your observations/conclusions at jira.iotivity.org? emails tend not to get formal enough attention from enough or the right people - it's good for discussion, but not so good for tracking issues. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9802): https://lists.iotivity.org/g/iotivity-dev/message/9802 Mute This Topic: https://lists.iotivity.org/mt/23791382/21656 Group Owner: [email protected] Unsubscribe: https://lists.iotivity.org/g/iotivity-dev/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
