ivity.org/pipermail/iotivity-dev/attachments/20161130/353481e4/attachment.html>
now it seems that a client first needs to look for a
resource directory; if there is one, use it. Otherwise set up periodic
discovery and maintain own resource/device list.
Thanks,
Zoltan
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20161130/c2175a9a/attachment.html>
vity-dev/attachments/20161130/953da777/attachment.html>
rt --
HTML ?? ??...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20161130/2bd3de05/attachment.html>
-- next part --
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 13614 bytes
Desc: ???
.
How could I make sure those server are really work with TLS ? How could I
test them ?
Best Regards,
El Lai.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20161130/80c79ba6/attachment.html>
___
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20161130/cf78cd9a/attachment.html>
up with unanticipated ways to use it.
(nothing wrong with that.)
can you give more details about your use case?
>
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20161130/068ec27b/attachment.html>
ce/device directory should be able to encapsulate this - is a
> resource directory guaranteed to be in the OCF network nowadays?
>
> I wonder what are the recommended client work flows the current OCF Core
> spec is supporting. Right now it seems that a client first needs to look
> for a resource directory; if there is one, use it. Otherwise set up
> periodic discovery and maintain own resource/device list.
>
>
>
> Thanks,
>
> Zoltan
>
>
>
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20161130/e6575352/attachment.html>
Hello,
after upgrading my Iotivity dependency from 1.1.0 to 1.1.1, I observe
the following regression.
Whenever I perform a PUT, more often than not I will observe the
following segmentation fault:
I/DEBUG ( 2776): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x35
I/DEBUG ( 2776):
ED_TLS: => free
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20161130/be8f11b6/attachment.html>
Hi,
About MIPS support, I wish I could investigate more on portability issue
but I have no hardware for.
Anyway let me share this known issue about a lib we're using in some
unit tests,
https://github.com/dascandy/hippomocks/pull/50
if you want to help feel free to comment above link.
I know t
nd the scope of a protocol specification. A
Resource Directory is an optimization; some networks need it, some don't;
it's not for the protocol to say. For example, a single client talking to
a single server is a network that obviously does not need an RD.
-Gregg
-- next part
ed dissemination, disclosure
or copying of the contents of this e-mail, or any similar action, is prohibited.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20161130/6570d159/attachment.html>
-
service.
For more information please visit http://www.symanteccloud.com
__
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20161130/4605fd19/attachment.html>
14 matches
Mail list logo