Rephrasing my question... In IoTivity 1.3.0 , under bridging project there are few plugins (Hue, LifX ...) which are based on the principle of Bridging Non-OCF ecosystem.
An IoTivity Client is developed to interact with the resources created by these plugins Only (and not to support real OCF devices). [This IoTivity Client is a console based application for user Interaction] In this architecture is implementing Provisioning and Ownership Transfer required ? On Nov 28, 2017 10:31 AM, "Thiago Macieira" <[email protected]> wrote: > On Monday, 27 November 2017 20:48:52 PST UDAY M. S wrote: > > In a architecture where there is a dedicated IoTivity Client whose > design is > > closely in sync with the Non-OCF Bridge Server and the server is not > > intended to be part of any other OCF network, also both Client and > Server > > runs on a same system. > > > > In this case, implementing Provisioning and Security is necessary ? > > How is it an OCF client if it only talks to non-OCF devices? > > -- > Thiago Macieira - thiago.macieira (AT) intel.com > Software Architect - Intel Open Source Technology Center > >
_______________________________________________ iotivity-dev mailing list [email protected] https://lists.iotivity.org/mailman/listinfo/iotivity-dev
