[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 12:52:56 +0000 (12:52 +0000)
commitcbc5e63127b53bb2adf13c4a81fe8024ac1272dc
tree10cf8c6086acddea5d986f3b7676e7aa1c393114
parentc1c9783fb7b4b7ebcf73e48415aa5b31052be63a
[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/3595
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]