locked
No Async Functions for Cryptography

    Question

  • I wonder why there is no asynchronous API in the Windows.Security.Cryptography.Core namespace.

    It would be my guess that cryptographic functions are computational expensive by nature and would benefit from asynchronous handling.

    Of course it is possible to read in data in chunks that get passed to CryptographicEngine::hashData et al but it seems a break from the usual API design so I was wondering if there was a special reason for this.

    Friday, December 14, 2012 2:57 PM

All replies

  • I am wondering the same.  Were you able to get an answer on this anywhere?
    Wednesday, February 13, 2013 4:04 PM