Adding Jed and generalizing subject:

Jed, it does not sound like we will get the core crypto landed without 
organizational effort and some luck:

  https://bugzilla.mozilla.org/show_bug.cgi?id=554827#c18

Are you comfortable allowing Q/A to be the arbiter of acceptable performance on 
device?

----- Original Message -----
From: "Richard Pappalardo" <[email protected]>
To: "Jared Hirsch" <[email protected]>, "No-Jun Park" <[email protected]>, 
"Sam Penrose" <[email protected]>
Cc: [email protected]
Sent: Thursday, May 15, 2014 12:48:48 PM
Subject: re: 968567


Just a quick follow-up... 

No-Jun and I were just discussing this and though we both agree that it's slow, 
there are some user experience actions where 'perceived' slowness seems less 
critical. Ideally, we'd like every component of our applications to be 
lightning fast, but as a user, it doesn't seem like it would  necessarily be 
perceived as abusive, since it's part of the one-time 'setup' experience.   If 
it seems realistic that we can make it better, great.  But if it's going to 
take enormous effort to get this moving (and it's not likely that's going to 
happen), should we consider closing this?

Bug 968567 - Expose the NSS implementation of PBKDF2 HMAC SHA256 from bug 
974162 to chrome JS for use by FxAccounts
_______________________________________________
Dev-fxacct mailing list
[email protected]
https://mail.mozilla.org/listinfo/dev-fxacct
  • re: 968567 Richard Pappalardo
    • FxA crypto performance on device (Re: 968567) Sam Penrose

Reply via email to