d never need to make a secured/unsecured distinction. of
course apps can still designate resources as secure or not but that is a
completely separate topic.
my 2 cents.
gregg
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160921/c28d8dad/attachment.html>
I created A Jira ticket to change the default flag for SECURED from '0' to '1'
https://jira.iotivity.org/browse/IOT-1320
I have created the change and committed it:
https://gerrit.iotivity.org/gerrit/#/c/12085/
The Android and Arduino builds would not build when the SECURED=1 flag was
used. I d
zed by persistent storage, and client code should not have to
separately call an init function for persistent storage. in other words
there should not be two ways to get going, one for SECURED=0 and one for
SECURED=1. client app code should never need to make a secured/unsecured
distinctio
e to plan to have a weekly CC on every Wed.
As the first CC for this coming release, I arranged time tomorrow as
follows.
Time: 7/9 (Wed) 16:00~17:00. KST (Asia/Europe)
Time: 7/10 (Thu) 9:00~10:00. KST (North America)
Please notify if you want to attend it.
Otherwise I?ll close to set up slot.
I?ll share the detail CC info tomorrow.
BR, Uze Choi
-- next part --
HTML ?? ??...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160921/d8792f47/attachment.html>
On quarta-feira, 21 de setembro de 2016 15:02:15 PDT Nash, George wrote:
> 20:02:51 *** Error:
> 20:02:51 * Please download mbedtls
> using the following command:* 20:02:51 * $
> git clone https
uld not have to
separately call an init function for persistent storage. in other words
there should not be two ways to get going, one for SECURED=0 and one for
SECURED=1. client app code should never need to make a secured/unsecured
distinction. of course apps can still designate resources as secure or not
but that is a completely separate topic.
>
> my 2 cents.
>
> gregg
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160921/86054a0c/attachment.html>
u
maxi.wu at u-media.com.tw
tel: +886 3 579 7969 ext 8319
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160921/86ab435e/attachment.html>
ail CC info tomorrow.
BR, Uze Choi
-- next part --
HTML ?? ??...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160921/42aeab71/attachment.html>
set up slot.
I?ll share the detail CC info tomorrow.
BR, Uze Choi
-- next part --
HTML ?? ??...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160921/0761e670/attachment.html>
text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: Digital signature
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160921/ce13d224/attachment.sig>
Hi Trevor,
There are lots of meaningless Android build checks.
I pushed the code to resolve this issue on master/1.2-rel branch together.
https://gerrit.iotivity.org/gerrit/#/c/12023/
Could you trigger only build_android removing below 12 android builds.
(./auto_build.sh android)
I create the bu
was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160921/3818d3de/attachment.html>
.iotivity.org/pipermail/iotivity-dev/attachments/20160921/7984ba67/attachment.html>
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160921/bbeb2960/attachment.html>
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 13402 bytes
Desc: not availab
--
HTML ?? ??...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160921/29be3e1a/attachment.html>
On quarta-feira, 21 de setembro de 2016 14:35:56 PDT shreyas Shah wrote:
> Hii ALL,
>
>
> I want detail information about how multicasting works in IoTivity-1.1.0.
IoTivity sends a multicast packet to the CoAP All-Nodes address, on the CoAP
port, unencrypted. Each node receives the multicast qu
0
1.2-rel: 26c2c38f58952004577e29e7d5dc9002e7ff8f30
Regards,
Trevor Bramwell
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: Digital signature
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachm
achment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160921/4a78aeee/attachment.html>
Hi Trevor,
There are lots of meaningless Android build checks.
I pushed the code to resolve this issue on master/1.2-rel branch together.
https://gerrit.iotivity.org/gerrit/#/c/12023/
Could you trigger only build_android removing below 12 android builds.
(./auto_build.sh android)
I create the bu
HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160921/5296d355/attachment.html>
20 matches
Mail list logo