@gpean is the need to schedule work on a separate thread for an existing module or something new ?

[damnboy]

Originally posted by @mhdawson in nodejs/node#13512 (comment)

[damnboy]

I am trying to move massca into nodejs env(as an addon),
in the main function of this project, it creates serveral threads waiting for the packet coming back which uses libcap). These threads never get close until the scan task is done,so these threads seems not fit into the Worker Poll.
As the guide book on the nodejs office site, you should never block the Event Loop and the Work Pool.
But the implementation of napi_create_async_work only corporate with the Worker Pool, not create a new thread.
Is there any easy way more than use the libuv APIs directly for thread creating?
Thanks.

[Trott]

@nodejs/workers @nodejs/n-api

(Should this be moved to the help repo?)

[Trott]

I'm going to move this to the help repo in the hopes that it attracts attention there that it is not getting here. If that's not the right repo, feel free to comment (or if you're an org owner, move it back yourself if you'd like!).

[gireeshpunathil]

@damnboy - is this still pending?

[gireeshpunathil]

inactive, closing