Skip to content
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

Can you explain the deployment architecture in the docs? #21

Closed
gargleblaster opened this issue Apr 6, 2015 · 3 comments
Closed

Can you explain the deployment architecture in the docs? #21

gargleblaster opened this issue Apr 6, 2015 · 3 comments

Comments

@gargleblaster
Copy link

May be a naive question, but I don't understand how TA-lib, written in C++, is deployed with this Node wrapper. Is it a separate process from Node, or are they somehow running in the same process?

@oransel
Copy link
Owner

oransel commented Apr 6, 2015

The core library is written in C++, but it is integrated into a node module. Execution is async.

@oransel oransel closed this as completed Apr 6, 2015
@gargleblaster
Copy link
Author

Are you saying that the C++ code runs within the Node vm?? Or is it a separate process started by Node? What O/S is the C++ compiled for? Does the user of the library need to start TA-lib, or is the entire thing managed by your Node module? I think this topic deserves some explanation in the docs.

@oransel
Copy link
Owner

oransel commented Apr 15, 2015

Module is instantiation is in the main process. Calculation work runs asynchronously via libuv. Once the work is done, results are queued to the callback function provided. These are very standard node.js conventions.

Due to the nature of these types of async libraries, you don't need to start it as you would in other platforms.

The module is compiled on the target platform during installation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants