[dev] node.js bindings: How to distinguish public API from private API

> -Original Message- > From: Warburton, David > Sent: Monday, April 13, 2015 9:27 AM > To: Lankswert, Patrick > Cc: Schulhof, Gabriel; Hudson, Douglas; iotivity-dev at lists.iotivity.org > Subject: Re: [dev] node.js bindings: How to distinguish public API from > pri

[dev] node.js bindings: How to distinguish public API from private API

t: Monday, April 13, 2015 9:09 AM >> To: Schulhof, Gabriel; Hudson, Douglas >> Cc: iotivity-dev at lists.iotivity.org >> Subject: Re: [dev] node.js bindings: How to distinguish public API from >> private API >> >> Hi Gabriel, >> >> Last week Dou

[dev] node.js bindings: How to distinguish public API from private API

lists.iotivity.org > Subject: Re: [dev] node.js bindings: How to distinguish public API from > private API > > Hi Gabriel, > > Last week Doug Hudson and I threw together a NodeJS wrapper for IoTivity > to take to the 1st build hackathon last weekend, you can check it

[dev] node.js bindings: How to distinguish public API from private API

Hi Gabriel, Last week Doug Hudson and I threw together a NodeJS wrapper for IoTivity to take to the 1st build hackathon last weekend, you can check it out here: https://github.com/dwarburt/iotivity_wrapper Instead of trying to expose the IoTivity functions one-to-one to NodeJS we took the appr

[dev] node.js bindings: How to distinguish public API from private API

Hi! I am making progress on my node.js bindings for iotivity: - I'm downloading the 0.9.0 C API using bower. This means I'm grabbing the followings: - resource/csdk - resource/oc_logger/c - resource/oc_logger/include - extlibs/cjson - I'm building it using node-gyp and linking it statical