Harish,
I appreciate your point of view, but actually having the application take over 
control of the notification is a bad idea. The behavior of observation is very 
clear and not negotiable. Leaving this behavior to the application opens the 
door for violation of software/network standard contract and should be 
discouraged.
If you want a behavior that is like observe, but not exactly observe, you 
should design an alternate notification mechanism.
That said, I will look at your changes. If they do not break the observe 
contract, I will accept them.
Pat

From: Harish Kumara Marappa [mailto:[email protected]]
Sent: Tuesday, September 01, 2015 5:56 AM
To: Lankswert, Patrick
Cc: uzchoi at samsung.com; iotivity-dev at lists.iotivity.org
Subject: Adding address and port information for ObservationInfo structure.


Hi Mr. Patrick,



We have requirement in simulator module of providing more information about 
observer rather than just giving the observation id.

>From application point of view it make sense if user has more information 
>about observer to take the control of notifying his interested observers.

We have modified RI C++ layer in the same regard and submitted patch for review 
https://gerrit.iotivity.org/gerrit/#/c/2323/.

Please provide your inputs on the change set.





Regards,

Harish Kumara M





[cid:image001.gif at 01D0E4A6.953E0C40]

[Image removed by sender.]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150901/2361db16/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ~WRD000.jpg
Type: image/jpeg
Size: 823 bytes
Desc: ~WRD000.jpg
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150901/2361db16/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 13168 bytes
Desc: image001.gif
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150901/2361db16/attachment.gif>

Reply via email to