On Thursday, 7 January 2016 11:07:34 UTC+10:30, Jeffrey Walton wrote: > > > > On Tuesday, January 5, 2016 at 10:24:48 PM UTC-5, Atton Mathews wrote: >> >> I've tried multithreading AES however it seems to crash in every once the >> limit of the buffer... >> > > Crypto++ is thread safe at the class level, meaning there is no shared > data among class objects. When you want multiple threads to access the same > class object, you have to provide the locks and barriers. > > Jeff >
Please elaborate on how that would be achieved, is there a reference somewhere I should use? -- -- You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to cryptopp-users-unsubscr...@googlegroups.com. More information about Crypto++ and this group is available at http://www.cryptopp.com. --- You received this message because you are subscribed to the Google Groups "Crypto++ Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to cryptopp-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
