That's a good suggestion, and might actually work for a lot of cases. It just came to my mind that scheduling them at the exact same time might actually cause performance and memory problems. Maybe one would've to start them a bit more sequentially.
On Sat, Feb 7, 2009 at 7:56 PM, Greg White <[email protected]> wrote: > > > On Sat, Feb 7, 2009 at 1:19 PM, Christoph Studer <[email protected]> wrote: >> >> Would it make sense to create a central scheduler for services that >> need to run periodically? >> >> There are a lot of application that want to run at periodic intervals, >> require network access and need to keep the device awake during their >> work. Instead of each app having to use an AlarmManager, a WakeLock >> and its own network availability checking / auto-retry, wouldn't it >> make sense to provide an API that would do that work? > > I think this is a great idea and something that could be of great value, but > all I want is something much simpler. I think that a flag to > AlarmManager.setRepeating specifying that the alarm can be adjusted in > order to synchronize multiple background tasks would be entirely > sufficient. Alternatively, a note that background tasks should adjust their > alarms to fire on the minute (or on five minute boundaries) would serve a > similar purpose. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
