avoid blocking the event loop in the async version about pbkdf2

[dcousens]

I'd rather not. This is a problem better dealt with by web workers, which must be done at a higher level in the application.

[calvinmetcalf]

periodically releasing control of the event loop during a long running async process would actually even be helpful in a web worker, from my experience workers are expensive to create so you end up only making a few so being able to respond to other messages while doing a long pbkdf2 wouldn't be the worst thing.

[dcousens]

But would that conform to the node API behavior?
On 23 Apr 2015 10:55, "Calvin Metcalf" [email protected] wrote:

periodically releasing control of the event loop during a long running
async process would actually even be helpful in a web worker, from my
experience workers are expensive to create so you end up only making a few
so being able to respond to other messages while doing a long pbkdf2
wouldn't be the worst thing.

—
Reply to this email directly or view it on GitHub
#15 (comment)
.

[calvinmetcalf]

the async one we'd be able to do it, let me whip something up

On Wed, Apr 22, 2015 at 11:18 PM Daniel Cousens [email protected]
wrote:

But would that conform to the node API behavior?
On 23 Apr 2015 10:55, "Calvin Metcalf" [email protected] wrote:

periodically releasing control of the event loop during a long running
async process would actually even be helpful in a web worker, from my
experience workers are expensive to create so you end up only making a
few
so being able to respond to other messages while doing a long pbkdf2
wouldn't be the worst thing.

—
Reply to this email directly or view it on GitHub
<
#15 (comment)

.

—
Reply to this email directly or view it on GitHub
#15 (comment)
.

[dcousens]

still the case?

Nope