Author: Kevin Galligan

On several projects we’ve needed the ability to sync stuff offline.  We’ve tried a number of approaches, and eventually wound up building a call bus service.

The basic idea behind the sync call bus is you post a command to the service, it adds it to a queue, and attempts to process the command.  The bus keeps commands in order, processes them one at a time, and will persist the command to be run later if the system can’t handle the command now, generally because you don’t have a network connection.

If you look back at my earlier post, android sqlite locking, I demonstrated that more than one sqlite connection was really bad. Bad-bad. OK, so now what? How do you keep one connection and manage it?