thaler
thaler copied to clipboard
Problem: no nodejs binding to the c api
https://github.com/node-ffi/node-ffi It can be used by:
- typescript integration tests
- sample wallet
I think this issue may be potentially moved to cro-nodelib? Currently, Node.js library is having these Neon wrapper native bindings: https://github.com/crypto-com/cro-nodelib/tree/master/native/src
neon bindings uses c , but i think support bindings based upon c-bindings also make sense.
May I know more about the context, what's the purpose to introduce node-ffi here? And how does it relate to the c-binding?
May I know more about the context, what's the purpose to introduce node-ffi here? And how does it relate to the c-binding?
Currently we have a c api which exposed all client-rpc functionality through unified api, and a python binding to it(https://github.com/crypto-com/chain/blob/master/integration-tests/bot/chainbinding.py), the python integration tests had switched to use it, works well. So a nodejs binding to it would be useful too, no need for client-rpc server in many situations.