Hi, I (strongly?) suggest you wrap access to the sqlite3 database in a Content Provider if you are accessing concurrently (doing both read&write) from Activity & Service - particularly if Service is in different process.
Content Provider seems to manage concurrent access for you ok, without having to get involved with semaphores/synchronization yourself. Regards On Apr 1, 9:21 am, lbendlin <l...@bendlin.us> wrote: > yes, semaphores are the way to go, especially for bulk write operations. it > helps if you read some of the data from the database into a buffer. Then you > can use the buffered data while the database update is processed, and the > users may not even notice. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
