On Monday, August 10, 2015 at 3:18:56 AM UTC-4, Ilya Bizyaev wrote: > > Yes, I now see there's no sense in multithreading for my app. When using > GUI mode, the speed is about 256 Mib/s, in console mode - about 532 Mib/s. > That's pretty much, and I won't use multithreading. Thanks, Jeffrey! >
Yeah, what you could do, if interested (its how I've handled it in the past): have the main thread service the GUI; and create a second worker thread for the crypto. You won't need synchronization objects per se because the GUI thread does not touch the Crypto++ objects. The app will stay responsive because the GUI thread is free to handle the clicks and swipes. There is some overhead with a GUI thread/worker thread. They must synchronize to start a task, cancel a task, inform when a task is complete, etc. For that, take a look at libevent and the asynchronous notifications. libevent supports Windows, Linux, Unix, OS X, BSDs, etc. Write once, run everywhere.... Jeff -- -- You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to [email protected]. 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
