New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Complete OCF #566

Open
hs0225 opened this Issue Nov 25, 2016 · 5 comments

Comments

Projects
None yet
7 participants
@hs0225
Contributor

hs0225 commented Nov 25, 2016

Implement OCF(Open Connectivity Foundation)

  • core

    • initialize
    • get_properties
    • setup_properties
    • free_ocf
  • server

    • initialize
    • create_resource
    • create_response
    • create_request
    • get_handler
    • put_handler
    • delete_handler
    • post_handler
    • notify
    • register
  • client

    • initialize
    • create_handler
    • get_handler
    • create_url
    • find_device
    • find_resource
    • create_resource
    • add_resource
    • create
    • update
    • delete

@hs0225 hs0225 added the API label Nov 25, 2016

@nova0821 nova0821 added this to the Release version 1.0 milestone Nov 25, 2016

@LaszloLango

This comment has been minimized.

Contributor

LaszloLango commented Nov 25, 2016

What is the motivation of re-implementing instead of using iotivity-constrained?

@RedCarrottt

This comment has been minimized.

Contributor

RedCarrottt commented Nov 25, 2016

I have a great interest in OCF support of IoT.js since I have a plan to make a graduate school lecture covering IoT.js and IoTivity.
Does the OCF IoT.js module just use existing IoTivity or IoTivity-constrained as a library?

@yichoi

This comment has been minimized.

Contributor

yichoi commented Nov 28, 2016

@LaszloLango Basically, I am going to use iotivity-constrained however As far as I know, iotivity-constrained does not support nuttx and our target (you might aware of this). I am thinking whether we should implement iotivity-constrained for nuttx and our target. Alternatively, I could assume that there will be implementation of iotivity-constrained for nuttx and our target then only support Linux for a while.

@hs0225 hs0225 removed this from the Release version 1.0 milestone May 16, 2017

@rzr

This comment has been minimized.

Contributor

rzr commented Mar 6, 2018

As some of you already know, parts (csdk) of iotivity 1.2-rel and 1.3-rel are already in TizenRT (so could be easly ported ported to nuttx), iotvivity-constrained works too on Tizen or Linux, but I am not aware about any attempt to port to nuttx/tinyara.

Also check related projects: zephyr.js (with IoTivity-contrained) and iotivity-node (based on regular IoTivity), maybe they can be aligned (at least licenses are same).

@haesik

This comment has been minimized.

Contributor

haesik commented Mar 7, 2018

@rzr Yes, I know iotivity 1.2 and 1.3 are already in the TizenRT and Tizen also support iotivity.
But I think the device-cloud model is more useful in IoT scenario, so we are focused on supporting SmartThings internally(that is also based on iotivity). Consequentially, we don't have enough human resource to support iotivity now and I am not sure when we can start it..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment