Hi!
At least for IoTivity it should be fairly simple to port it to RIOT according
to the response I got on their mailing list:
http://lists.iotivity.org/pipermail/iotivity-dev/2015-March/000600.html
The only problem I see is the incompatible license of their implementation.
(Btw. the Contiki
Hi!
I just realized that I'll probably learn something about IoTivity and AllJoyn
today at the T2TRG meeting:
https://github.com/t2trg/2015-ietf92/blob/master/agenda.md
I guess there won't be now audio stream, but at least the slides should be
online later this day.
Concerning IoTBase, I
Oleg Hahm wrote:
I (and I guess I'm speaking for most of us) want a
(R)IOT device being able to be connected _directly_ to anything. Be it another
RIOT powered device, a Contiki device, my home gateway, my smartphone, or any
server in the Internet.
That's why it's called Thing-to-thing
Hello Baptiste!
2015-03-20 9:02 GMT+01:00 Baptiste Clenet bapcle...@gmail.com:
I agree with you about IETF protocols, everybody should use them and it
will make communication easier.
In my opinion IETF protocols have the most potential to become de facto
standards. However IETF doesn't
Hi Rioters,
This question is not particularly about Riot but it makes sense to ask you
since future Riot device might use one of this high level protocol
(Iotivity, AllJoyn, Thread, Ipso Alliance).
What do you think about them? In your opinion, which one will be mostly
used?
Is there any future
