On Wed, Feb 28, 2018 at 4:09 PM, Thiago Macieira
wrote:
> On Wednesday, 28 February 2018 12:19:48 PST Nash, George wrote:
> > So far in all of the services that I have developed I have always created
> > the resource as soon as the service is started.
> >
> > However, CRUDN is CREATE, READ, UPDA
On Wednesday, 28 February 2018 12:19:48 PST Nash, George wrote:
> So far in all of the services that I have developed I have always created
> the resource as soon as the service is started.
>
> However, CRUDN is CREATE, READ, UPDATE, DELETE, NOTIFY.
>
> I CREATE the resource at service start as
On Feb 28, 2018 2:19 PM, "Nash, George" wrote:
So far in all of the services that I have developed I have always created
the resource as soon as the service is started.
Presumably you mean in code, not involving a CREATE msg.
However, CRUDN is CREATE, READ, UPDATE, DELETE, NOTIFY.
I CREAT
So far in all of the services that I have developed I have always created the
resource as soon as the service is started.
However, CRUDN is CREATE, READ, UPDATE, DELETE, NOTIFY.
I CREATE the resource at service start as part of the initialization code.
Should I wait for a client action before
On Feb 28, 2018 1:08 PM, "Heldt-Sheller, Nathan" <
nathan.heldt-shel...@intel.com> wrote:
...
we expect vendor OBTs will use the forthcoming OBT from Dekra.
Whassat?
___
iotivity-dev mailing list
iotivity-dev@lists.iotivity.org
https://lists.iotivity.o
I’ve created a JIRA ticket and assigned to Aleksey:
https://jira.iotivity.org/browse/IOT-3001
However (admittedly not having had much time to look at it yet) this is
actually a provisioningclient example app bug, I think. The rowneruuid of the
/cred Resource should be explicitly set by the OBT
Should we create a Jira ticket for this issue so it can be tracked?
Also Ravee reported the issue for 1.3.1 should we check the fix into the 1.3
branch?
George Nash
From: iotivity-dev-boun...@lists.iotivity.org
[mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of Oleksiy Volkov
Sent:
Hi Ravee,
By default, Client #2 can only discover resources after otm, but doesn't have access to them.
But Client #1 can provision additional credential and acl records regarding Client #2 to device, and Client #2 will have access to certain resources on this device after onboarding.
T
Hi Ravee,
you are right, this is a bug.
I prepared a fix: https://gerrit.iotivity.org/gerrit/#/c/24239/, you can use it for your tests.
Best regards,
Aleksey Volkov
- Original Message -
Sender : Raveendranath Kondrakunta
Date : 2018-02-28 11:22 (GMT+2)
Title
Hi Nathan,
Sorry, I've a typo in the earlier mail.
- In the persistent store(oic_svr_db_server.dat and
oic_svr_db_client.dat) *rowneruuid* of the Owner Credential (OC) stored
as *nil uuid*.
Test setup
1. Using release 1.3.1
2. Created my svr db files(both client and server) with
10 matches
Mail list logo
