GeezIHateCreatingNewNames wrote: > The more complicated case > seems to be a single application that has two processes in it (e.g, an > application with a long running service).
You do not need two processes for an application with a long running service. Not to mention that long-running services aren't a great idea in the first place. > In this case it seems like > you could simply share at the sqlite database layers, but the locking > and sharing story on the sqlite database APIs is somewhat unclear. SQLite handles cross-process locking. That's one of the reasons why it is the default database for Rails and other Ruby server-side frameworks that rely on multiple processes. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy Android Development Wiki: http://wiki.andmob.org --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
