Hi Thiago, Theoretically everything could be changed. However, we can expect that IP can be maintained in the home from most of cases.
The whole process execution of ?Discovery some list of devices and identify one of them? need to be avoid as much as possible once it has been done. So that port num. random generation policy does not fit this requirement I think. Even though Dynamic port num. increment is good feature. Additionally, providing the way to fix device id is essential also for the same reason above. Even though we deliver the OIC secure mode product, we should test it from non-secure mode. Either fixing the device regardless of non-secure mode or secure mode or API of setting the device id will be resolve the issue. When reminding the UPnP use case, uuid is not usually updated in the product whenever power on again so that, discovery and selection of device is not done from user which relieve the intriguing user interaction. Jon, what is your opinion? BR, Uze Choi From: [email protected] [mailto:iotivity-dev- bounces at lists.iotivity.org] On Behalf Of ??? Sent: Friday, January 22, 2016 2:47 PM To: Thiago Macieira; iotivity-dev at lists.iotivity.org Subject: Re: [dev] Need API to set static "sid" and "port number". - OCDoResource() must set port number. How can forget it? If you right, then iotivity should be redesign. Because, OCDoResource() has port number dependency. If we support just one optional api, we can reduce re-discovery problem. I don't understand why did yoy object to add "OPTIONAL" api although it can provide very useful user exprience. And, old version iotivity could set port number... there is no issue about development ------- Original Message ------- Sender : Thiago Macieira<thiago.macieira at intel.com> Date : 2016-01-22 14:19 (GMT+09:00) Title : Re: [dev] Need API to set static "sid" and "port number". On Friday 22 January 2016 02:25:47 jaekeun lee wrote: > I didn't say that change the mechanism. > I said, support the additional API for set to port number and sid or > di(variable name is sid) is very useful and helpful. > The experience depends on how the application is written > How can fix this issue? > - Presence Check -> Re-Discovery -> Check saved DI & discovered DI -> change > target's IP/PORT or > - re configure every run > These are very inconvenience . > > But, if server can set port, then re-configure only when server not work(may > be ip changed or port occupied). > Just additional API. Forget the port number. If your other side is trying to depend on the port number, please redesign it. You cannot count on the port number being free, so your other side must be able to deal with the port number changing. For that matter, the IP might change after a reboot. Or even without a reboot: IPv6 temporary addresses change about once a day. Since you can't count on the IP being fixed, port numbers don't identify anything. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center <http://ext.samsung.net/mailcheck/SeenTimeChecker?do=28bccb0e7a1e0d0665c2278 d83f0484165a4919a5534baf50cf2282830c3416bfcfabd80c3fe6049141ee34884fd53a813d 69ea60670f66ef4bcdeced46ed5ee08cece8541bc14eacf878f9a26ce15a0> -------------- next part -------------- HTML ?????? ??????????????... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160122/b4cb9f1c/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 13168 bytes Desc: ?????? ?? ????????. URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160122/b4cb9f1c/attachment.gif>
