Hi,
You can check OC::OCResource:: getAllHosts() API which returns a vector of endpoint strings.
Below is a sample of items inside returned vector for a resource which supports multiple endpoints :
1. coaps://192.168.1.102:353072. coaps://[fe80::ea11:32ff:fe67:7f5d%25p10p1]:464213.
On Dec 12, 2017 6:18 PM, "Mats Wichmann" wrote:
On 12/12/2017 04:33 PM, Gregg Reynolds wrote:
> On Dec 11, 2017 2:41 PM, "Gregg Reynolds" wrote:
>
> Ditto for the Cloud stuff - nice, I guess, but
> what is it doing in the core Iotivity project?
>
>
> Not to mention "presence", which looks to me
On 12/12/2017 04:27 PM, Gregg Reynolds wrote:
> On Dec 12, 2017 5:16 PM, "Morrow, Joseph L"
> wrote:
>
> Hi David,
>
> Presence does not align with “Advertisement.” You will not get notified
> when a new server comes online.
>
> A way to achieve this is to implement a Resource Directory in your
Ah, yes, " You will not get notified when a new server comes online.". But
that would be true for each server that calls startPresence()?
On Tue, Dec 12, 2017 at 3:16 PM, Morrow, Joseph L wrote:
> Hi David,
>
> Presence does not align with “Advertisement.” You will not get notified
> when a new
Hey guys, thanks. I was able to fix my issue by setting it all to
CT_IP_USE_V4.
Joseph - thanks for the clarity on this. it does seem that presence is a
bit more generic than resources since IoTivity only provides the
hostAddress of the presence. Nothing about which resource, etc initiated it.
Yo
On 12/12/2017 04:33 PM, Gregg Reynolds wrote:
> On Dec 11, 2017 2:41 PM, "Gregg Reynolds" wrote:
>
> Ditto for the Cloud stuff - nice, I guess, but
> what is it doing in the core Iotivity project?
>
>
> Not to mention "presence", which looks to me like a non-ocf feature.
>
> G
It's always be
I don’t know. I guess you will need to have endpoint data for the RD apriori.
To reduce, the number of back-and-forth emails, I will also state that Presence
is a non-OCF feature as you suggest. It was an OIC feature. So, I would argue
it should become refactored out of the ‘oic’ namespace. I be
You may (I’m not completely sure as of now) get a notification if a server your
client has previously subscribedPresence for leaves and then comes back online
upon the server’s StartPresence(). However, you will not receive a notification
from a server you have never issues SubscribePresence() f
On Dec 11, 2017 2:41 PM, "Gregg Reynolds" wrote:
Hi Martin!
On Dec 11, 2017 5:20 AM, "Martin Roesch" wrote:
...
What scope do you have in mind?
Minimal OCF support. Iotivity is chock-full of add-ons. They're fine, but I
would prefer that add-ons be separate from the core engine. IOW I wou
On Dec 12, 2017 5:16 PM, "Morrow, Joseph L"
wrote:
Hi David,
Presence does not align with “Advertisement.” You will not get notified
when a new server comes online.
So Iotivity is non-compliant?
___
iotivity-dev mailing list
iotivity-dev@lists.iotivi
On Dec 12, 2017 5:16 PM, "Morrow, Joseph L"
wrote:
Hi David,
Presence does not align with “Advertisement.” You will not get notified
when a new server comes online.
A way to achieve this is to implement a Resource Directory in your set-up.
Assume every client observes the Resource Directory. As
Hi David,
Presence does not align with “Advertisement.” You will not get notified when a
new server comes online.
A way to achieve this is to implement a Resource Directory in your set-up.
Assume every client observes the Resource Directory. As per my understand, Then
every Server in your set-
The OIC Spec referred to IoTivity’s Presence feature as “Advertisement.”
Please do not mix up OIC’s use of the word “Advertisement” with my use of it at
the bottom of my email response below.
Thanks,
Joey Morrow
From: Joseph L Morrow
mailto:joseph.l.mor...@intel.com>>
Date: Tuesday, December
Hi Gregg,
The OIC spec used to have “Advertisement” specified. But in push to move OCF
and get a spec out, advertisement was removed. At the time, I recall someone
stated the intention was to bring it back immediately after OCF 1.0.
As you can see it never did.
I can give you some hints of wha
On Dec 12, 2017 10:03 AM, "David Brody" wrote:
..
Any help or clarity would be GREATLY appreciated. The documentation on this
is very limited and I've dug into the code a bit too far with no luck.
Sorry I cannot help, but if you don't mind I'll piggyback here and ask if
somebody can explain "p
It should be added that this appears to only be possible with the C SDK, not
the C++ SDK since the Discovery Callback function signature doesn’t provide
endpoint information.
If the client has to choose which version of a discovered resource to store and
act on (ie. Get/Post) later, there shoul
Hello,
The code I am working with has a pointer to a C++ OC::OCResource object and I
am trying to determine if the IoTivity endpoint is using COAP or COAPS. The
eps->tps member of the OCResourcePayload data structure can be used to
determine the transport type (i.e., COAP or COAPS). I don't kno
I have 3 of the exact same programs running on three different machines (2
raspberrypis and one mac OSX). The programs and all work well however I
cant get presence to work consistently.
The program is set to multicast presence and the platforms are all set to
ModeType::Both. They all generate uni
18 matches
Mail list logo
