Chromium Code Reviews| OLD | NEW |
|---|---|
| (Empty) | |
| 1 Provides the ability to block the device / display from sleeping. | |
|
Ken Rockot(use gerrit already)
2017/03/16 17:48:40
README.mojom?
dcheng
2017/03/17 06:55:26
Nit: should this be README.md?
blundell
2017/03/17 12:28:21
Who is README.mojom? My name is README.md.
blundell
2017/03/17 12:28:21
Who is README.mojom? My name is README.md.
| |
| 2 | |
| 3 On Android, the implementation is inherently coupled to the NativeView | |
| 4 associated with the context of the requestor due to system APIs. To handle | |
| 5 this coupling, the Wake Lock usage model on Android is as follows: | |
| 6 | |
| 7 (1) The embedder passes in a callback at Device Service construction that | |
| 8 enables the Wake Lock implementation to map (embedder-specific) context IDs to | |
| 9 NativeViews. | |
| 10 (2) For a given embedder-specific context, a trusted client | |
| 11 connects to the WakeLockContextProvider interface and gets a | |
| 12 WakeLockContext instance that is associated with that context. | |
| 13 (3) That trusted client then forwards requests to bind wake locks from | |
| 14 untrusted clients that are made within that context, with the Wake Lock | |
| 15 implementation using the callback from (1) as necessary to obtain the | |
| 16 NativeView associated with that context. | |
| 17 | |
| 18 On other platforms, the usage model is similar but the callback is not | |
| 19 necessary/employed. | |
| OLD | NEW |