Long running script warning

[GoogleCodeExporter]

Problem: Browsers will stop and display a warning when crypto operations takes 
too long to run (like PBKDF2 with large iteration). Means of detection browsers 
use varies, some measure actual time, others measuring # of statements.

Suggested solution: divide up crypto operations into smaller units and run each 
unit through a callback argument. With browsers, callback can be implemented 
using setTimeout or Web worker API. With Node.js, callback can call 
process.nextTick.

Original issue reported on code.google.com by super...@gmail.com on 7 Mar 2011 at 12:34

[GoogleCodeExporter]

Target release: v3.0.

Original comment by Jeff.Mott.OR on 7 Mar 2011 at 3:47

• Changed state: Accepted

[GoogleCodeExporter]

Original comment by Jeff.Mott.OR on 7 Mar 2011 at 3:51

• Added labels: Milestone-3.0

[GoogleCodeExporter]

Original comment by Jeff.Mott.OR on 7 Mar 2011 at 3:51

[GoogleCodeExporter]

Hi, you probably noticed by now but I posted two versions of async PBDKF2 on 
the discussion list to work with. Thanks for a great library BTW. - Don

Original comment by super...@gmail.com on 7 Mar 2011 at 8:08

[GoogleCodeExporter]

Hi Don,

Thanks! That's great work. I added your PBKDF2Async, and it'll roll out with a 
v2.1 release.

The commit details: http://code.google.com/p/crypto-js/source/detail?r=302

Original comment by Jeff.Mott.OR on 14 Mar 2011 at 5:16

• Changed state: Fixed
• Removed labels: Milestone-3.0