Use a single thread for DB access from the UI.
The UI may access the DB in response to UI or DB events; to maintain a consistent view of the DB's contents, the tasks performing these accesses must be prevented from overlapping, and must produce consistent results if reordered. A single-threaded executor and latches are used to prevent tasks from overlapping, without blocking non-UI access to the DB.
Showing
- briar-android/src/net/sf/briar/android/AndroidModule.java 7 additions, 0 deletionsbriar-android/src/net/sf/briar/android/AndroidModule.java
- briar-android/src/net/sf/briar/android/groups/GroupActivity.java 20 additions, 14 deletions...ndroid/src/net/sf/briar/android/groups/GroupActivity.java
- briar-android/src/net/sf/briar/android/groups/GroupListActivity.java 42 additions, 27 deletions...id/src/net/sf/briar/android/groups/GroupListActivity.java
- briar-android/src/net/sf/briar/android/messages/ConversationActivity.java 19 additions, 13 deletions...c/net/sf/briar/android/messages/ConversationActivity.java
- briar-android/src/net/sf/briar/android/messages/ConversationListActivity.java 53 additions, 37 deletions...t/sf/briar/android/messages/ConversationListActivity.java
- briar-api/src/net/sf/briar/api/android/DatabaseUiExecutor.java 18 additions, 0 deletions...-api/src/net/sf/briar/api/android/DatabaseUiExecutor.java
Loading
Please register or sign in to comment