Em sexta-feira, 6 de janeiro de 2017, ?s 15:48:01 PST, Richard Peters
escreveu:
> Hi Community,
>
> i am new to IOTivity and i have few questions to get started:
>
> 1. does the IOTivity-contrained libarary support gateway functionallity?
> I want to use a constrained device (cortex-m controller) as gateway
> between different types of links. Is this possible?
Hello Richard
It doesn't prevent you from doing gatewaying. The IoTivity Constrained code
allows you to turn both client and server sides of IoTivity on at the same
time, so you can easily send requests as an effect of receiving requests. The
gatewaying functionality itself is up to you ("application code").
However, it's not really what it's designed for. Constrained devices are
usually edge devices (leaf nodes), not routers.
> 2. can i use a constrained device that is actually an 6LoWPAN edge
> router as a bridge to an IOTivity cloud server (e.g. to forward requests
> to the cloud and vice versa) ?
To make sure we're using the same terms: by edge router, do you mean a border
router (6LBR)? If not, what do you mean?
You can do it ("application code"), but I advise against making a constrained
device talk directly to the Internet and the cloud. That task is much better
left to a more powerful device that provides security-in-depth techniques like
privilege separation and can be upgraded more easily.
> 3. can a constrained node be used to manage service discovery for other
> constrained nodes?
Sure, but again, what's the point? A constrained node is called that because
it is constrained: little RAM, little ROM and/or little battery capacity. If
it is managing things for others, it's not really constrained.
But IoTivity Constrained can be deployed on a non-constrained OS and device
(it runs on Linux). It's just not what it's designed for.
> Some hints to documentation and implementation guides that belong to
> these questions would be really welcome :-)
Everything except the access to the OCF protocol is up to you. How you receive
messages, send others as effect of that, keep track of where to send replies
to, time them out, etc., is stuff you need to write.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
