[email protected] writes: > In my opinion, using wakelock is not so intuitive for application > developer. Like the wakelock page indicates, "the risk of claiming the > lock is that users may forget to close the app when they are done > using it". Developers need to lock the service and unlock this service > carefully by themselves which sometimes might cause serious results.
No matter which approach you take, the risk of not releasing the resource is the same. One could still forget to clearWatch. > And Let's look at the cases on Android and IOS, they are also using > the way like the second suggestion which is telling the system that > they want their service runs in background and let service handle by > the system without needing to worry about it. The resource management behind option and wake lock is same; just the syntax is different. Kanru _______________________________________________ dev-geolocation mailing list [email protected] https://lists.mozilla.org/listinfo/dev-geolocation
