[dev] Host field ignored in findResource

> -Original Message- > From: iotivity-dev-bounces at lists.iotivity.org [mailto:iotivity-dev- > bounces at lists.iotivity.org] On Behalf Of Thiago Macieira > Sent: Sunday, March 01, 2015 11:18 PM > To: iotivity-dev at lists.iotivity.org > Subject: Re: [dev] Hos

[dev] Host field ignored in findResource

On Monday 02 March 2015 10:07:42 Thiago Macieira wrote: > > Yes, these interfaces are really effectively map to internal file handles. > > I'd much rather use the if_index / sin6_scope_id interface ID, since it's a > global number. The user won't be confused by a different index. > > An alternat

[dev] Host field ignored in findResource

On Monday 02 March 2015 08:22:38 Lankswert, Patrick wrote: > > What are the bits supposed to mean? Detecting the WAN interface may not > > be so simple. It might be possible to do this on the majority of cases by > > scanning the routing table, but it will fail on edge cases (e.g., my > > laptop wh

[dev] Host field ignored in findResource

On Friday 27 February 2015 13:50:55 Lankswert, Patrick wrote: > BSD sockets as the standard for IP communication clearly expresses UDP > packet > routing and interface expression. However, it is expressed several ways. > > 1) They are bound BEFORE use, but given it is bound to all interfaces > (in

[dev] Host field ignored in findResource

> -Original Message- > From: iotivity-dev-bounces at lists.iotivity.org [mailto:iotivity-dev- > bounces at lists.iotivity.org] On Behalf Of Thiago Macieira > Sent: Thursday, February 26, 2015 2:19 PM > To: iotivity-dev at lists.iotivity.org > Subject: Re: [dev] Hos

[dev] Host field ignored in findResource

> -Original Message- > From: iotivity-dev-bounces at lists.iotivity.org [mailto:iotivity-dev- > bounces at lists.iotivity.org] On Behalf Of Thiago Macieira > Sent: Thursday, February 26, 2015 12:52 PM > To: iotivity-dev at lists.iotivity.org > Subject: Re: [dev] Hos

[dev] Host field ignored in findResource

On Thursday 26 February 2015 10:03:21 Dieter, William R wrote: > For example, if IoTivity were integrated into a NAT firewall with one > Ethernet interface going to the outside world and one (or more) interfaces > on the inside network, the firewall would probably only want to find > devices by mul

[dev] Host field ignored in findResource

On Wednesday 25 February 2015 14:02:47 Kesavan, Vijay S wrote: > We support global discovery (all interfaces, all transports) and host > discovery (specific host on a specified transport - requires identification > information for that host eg. IP addr or MAC addr). Interface discovery > itself mi

[dev] Host field ignored in findResource

otivity.org] On Behalf Of Jon A. Cruz Sent: Wednesday, February 25, 2015 3:11 PM To: iotivity-dev at lists.iotivity.org Subject: Re: [dev] Host field ignored in findResource On 02/25/2015 02:02 PM, Kesavan, Vijay S wrote: > We support global discovery (all interfaces, all transports) and

[dev] Host field ignored in findResource

lists.iotivity.org [mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of Thiago Macieira Sent: Wednesday, February 25, 2015 1:52 PM To: iotivity-dev at lists.iotivity.org Subject: Re: [dev] Host field ignored in findResource On Wednesday 25 February 2015 19:59:56 Prasad, Sudarshan wrote

[dev] Host field ignored in findResource

ne, Erich; iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: Re: [dev] Host field ignored in findResource Complicating the issue in the current code base is that a network address in the second field is processed approximately the doc says the first arg

[dev] Host field ignored in findResource

-boun...@lists.iotivity.org] On Behalf Of Light, John J Sent: Wednesday, February 25, 2015 11:08 AM To: Keane, Erich; iotivity-dev at lists.iotivity.org Subject: Re: [dev] Host field ignored in findResource Complicating the issue in the current code base is that a network address in the second fie

[dev] Host field ignored in findResource

[mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of Light, John J Sent: Wednesday, February 25, 2015 10:48 AM To: iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: [dev] Host field ignored in findResource I submitted a JIRA on this, but I'd like a time

[dev] Host field ignored in findResource

Behalf Of Light, John J Sent: Wednesday, February 25, 2015 10:48 AM To: iotivity-dev at lists.iotivity.org Subject: [dev] Host field ignored in findResource I submitted a JIRA on this, but I'd like a timely answer since it affects IPv6 work. The first argument to Platform::findResource (and

[dev] Host field ignored in findResource

I submitted a JIRA on this, but I'd like a timely answer since it affects IPv6 work. The first argument to Platform::findResource (and Platform::findDevice) is ignored when the code reaches InProcClientWrapper::ListenForResource (or ListenForDevice). The field can be a host url, but documentat

[dev] Host field ignored in findResource

> > -Original Message- > From: iotivity-dev-bounces at lists.iotivity.org [mailto:iotivity-dev-bounces > at lists.iotivity.org] On Behalf Of Jon A. Cruz > Sent: Wednesday, February 25, 2015 3:11 PM > To: iotivity-dev at lists.iotivity.org > Subject: Re: [dev] Host fie

[dev] Host field ignored in findResource

On 02/25/2015 02:02 PM, Kesavan, Vijay S wrote: > We support global discovery (all interfaces, all transports) and host > discovery (specific host on a specified transport - requires identification > information for that host eg. IP addr or MAC addr). Interface discovery > itself might have s

[dev] Host field ignored in findResource

On Wednesday 25 February 2015 19:59:56 Prasad, Sudarshan wrote: > Next, while doing connectivity abstraction integration with the resource > introspection layer, there was an additional parameter (for connectivity > type. NOTE: This change is already in connectivity-abstraction branch. > Eventually