[IOT-762] Something wrong with handling unicast presence response - client always...
authordaeken.kwon <daeken.kwon@samsung.com>
Tue, 6 Oct 2015 05:32:32 +0000 (14:32 +0900)
committerPatrick Lankswert <patrick.lankswert@intel.com>
Tue, 6 Oct 2015 15:46:38 +0000 (15:46 +0000)
commit63fb9125f3e204305355c27461ebb919d74a3e30
treecca5fc51e49f7b60548fd9d63e3bb6ee5a52fb0c
parent38b974813a5978dc4ec9a5798d0a7c143b1dc46b
[IOT-762] Something wrong with handling unicast presence response - client always get "PRESENCE_TIMEOUT"

< Cause >
ocstack don't do ResetPresenceTTL() after getting presence response from server because there was no change in sequnceNumber

< Solution >
To resolve this case, it is just needed to put ResetPresenceTTL() before exit in this caseTo resolve this case, it seems that we just put ResetPresenceTTL() before exit in this case

Change-Id: If1e32692d3b859cea84382bded0cceecf42874d5
Signed-off-by: daeken.kwon <daeken.kwon@samsung.com>
Reviewed-on: https://gerrit.iotivity.org/gerrit/3581
Reviewed-by: Uze Choi <uzchoi@samsung.com>
Tested-by: jenkins-iotivity <jenkins-iotivity@opendaylight.org>
Reviewed-by: Patrick Lankswert <patrick.lankswert@intel.com>
resource/csdk/stack/src/ocstack.c [changed mode: 0644->0755]