The new IntentService in Android 1.5 looks excellent for handling
AlarmManager-initiated broadcasts for scheduled WAKEUP work...except I
can't see that it uses a WakeLock anywhere, either in itself or
Looper/MessageQueue.

Does this implicitly hold a WakeLock that I'm not seeing? Or would I
need to create a WakingIntentService that has an active WakeLock so long
as there are messages in the queue?

Thanks!

-- 
Mark Murphy (a Commons Guy)
http://commonsware.com | http://twitter.com/commonsguy

_The Busy Coder's Guide to Android Development_ Version 2.0 Available!

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to