On Thu, Feb 13, 2014 at 9:57 AM, WebDoctor <yassine.sa...@gmail.com> wrote:
>> > Should I write my own XPCOM object, or is there any other reasonable >> > solution for that?. And can any one collaborate with me create this >> > solution ? > Thank you, i'll try to test the verifyCertNow in my extension and see what > result i can get. If the verifyCertNow function works for you, then please file a bug about creating an asynchronous version of verifyCertNow. It is OK to use verifyCertNow for prototyping, but it is bad to use verifyCertNow in the final version of an extension. The reason is that verifyCertNow is synchronous, and it will block everything that Firefox does while it does the verification, and/or it will spin the event loop, which creates its own set of problems. If you file a bug for creating the async variant, I can either help you add it (this will be fastest, if you know how to add XPCOM APIs already), or I can find somebody to do it. Note to David and Camilo: We should change the tests that use this sync function to use the new async version, and remove the sync version. /** Warning: This interface is inteded to use only for testing only as: * 1. It can create IO on the main thread. * 2. It is in constant change, so in/out can change at any release. */ Cheers, Brian -- Mozilla Networking/Crypto/Security (Necko/NSS/PSM) -- dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
