One aspect here sounds like code is depending on IoTivity devices to operate like some other common servers where HTTP is on port 80, telnet is on port 23, ssh on port 22, SMTP is on port 25, etc. Compliance with company IT policies, firewall requirements, vpn rules, etc. might come into play there.
If this is so, then a question would be to ask if such port-bound services were counter to the OIC intent, within the OIC intent or un-addressed by it. On the other hand, if it is just code counting on finding a device by using address+port as a key, then I would share concerns on such software being fragile. On 01/22/2016 08:20 AM, Light, John J wrote: > Samsung Enterprise Portal mySingle > > Jack Lee (?), > > In OCDoResource, you can supply a port number in the OCDevAddr > argument. Network layer will use it, just as in original IoTivity. > So the same functionality exists. > > I still have reservations about the design of counting on port numbers > persisting. > > John > > *From:*iotivity-dev-bounces at lists.iotivity.org > [mailto:iotivity-dev-bounces at lists.iotivity.org] *On Behalf Of *??? > *Sent:* Thursday, January 21, 2016 9:47 PM > *To:* Macieira, Thiago; 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 > <mailto: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 > > > > _______________________________________________ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160125/f63ff809/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 13168 bytes Desc: not available URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160125/f63ff809/attachment.gif>
