- Nov 08, 2014
-
-
akwizgran authored
-
- Nov 05, 2014
- Oct 02, 2014
-
-
akwizgran authored
We don't need two separate executors for long-running IO threads.
-
- Jan 24, 2014
-
-
akwizgran authored
-
- Jan 14, 2014
-
-
akwizgran authored
-
- Jan 13, 2014
-
-
akwizgran authored
-
- Jan 08, 2014
-
-
akwizgran authored
-
- May 15, 2013
-
-
akwizgran authored
Fixes issue #3612607.
-
- May 04, 2013
-
-
akwizgran authored
CryptoExecutor and DatabaseExecutor now use bounded thread pools with unbounded queues, since running too many tasks in parallel is likely to harm performance; IncomingConnectionExecutor, PluginExecutor and ReliabilityExecutor use unbounded thread pools with direct handoff, since their tasks may run indefinitely. There are no longer any bounded executors, and all executors discard tasks when shutting down, which fixes issue #3612189. Responsibility for starting and stopping services has been moved from BriarService in briar-android to LifecycleManagerImpl in briar-core. However, BriarService is still responsible for stopping the Android-specific executors, which is ugly. It would be better if executors registered themselves with LifecycleManager.
-
- Apr 24, 2013
-
-
akwizgran authored
-
- Mar 29, 2013
-
-
akwizgran authored
The invitation and private messaging UIs are currently broken. Some key rotation bugs were fixed; others may have been created (unit tests needed). An encoding for private keys was added. Pseudonyms were moved out of the messaging package and ratings were moved in.
-
- Feb 12, 2013
- Jan 30, 2013
-
-
akwizgran authored
-
- Dec 15, 2012
-
-
akwizgran authored
This allows different plugins to have different dependencies without cluttering the plugin factory API.
-
- Dec 05, 2012
-
-
akwizgran authored
-