-
Notifications
You must be signed in to change notification settings - Fork 10
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
[WIP] Questions/Brainstorming #50
Comments
UpdatePer chat with @springmeyer when running through #51, I plan to:
|
|
@GretaCB thanks for catching up on skel today voice. To help get to the finish line for this phase I've reviewed all open issues and commented on ones that I think are actionable. Of those that are actionable I think these are the priority things to finish before you move along:
|
woot @GretaCB - everything above is checked. Shall we close? |
Per discussion with @springmeyer , outlining possible next steps for node-cpp-skel and capturing best practices to document and integrate into the skel design.
Questions to answer
What does it look like to have the variable that represents an instance of a class accessible in the threadpool?
What is the role of a singleton and how is it related to other design patterns for sync/async?
When passing data to thread pool, the data needs to be a type that is safe to pass into the thread pool. What makes a type safe to pass into the thread pool?
Designing skel:
Goal 1)
Goal 2)
Preliminary conclusion: object-sync is caught between these worlds
Terms to learn
Standard C++
static
keyword&
mean?)V8
Nan::Persistent
(which is reallyv8::Persistent
)v8::FunctionTemplate
andv8::Function
Nan::ObjectWrap
Possible next steps:
Two options:
shave
function access Filters as an argumentThe text was updated successfully, but these errors were encountered: