OLD | NEW |
| (Empty) |
1 /* Copyright (c) 2012 The Chromium Authors. All rights reserved. | |
2 * Use of this source code is governed by a BSD-style license that can be | |
3 * found in the LICENSE file. | |
4 */ | |
5 | |
6 /** | |
7 * Defines the PPB_MessageLoop_Dev interface. | |
8 */ | |
9 label Chrome { | |
10 M18 = 0.1 | |
11 }; | |
12 | |
13 /** | |
14 * A message loop allows PPAPI calls to be issued on a thread. You may not | |
15 * issue any API calls on a thread without creating a message loop. It also | |
16 * allows you to post work to the message loop for a thread. | |
17 * | |
18 * To process work posted to the message loop, as well as completion callbacks | |
19 * for asynchronous operations, you must run the message loop via Run(). | |
20 * | |
21 * Note the system manages the lifetime of the instance (and all associated | |
22 * resources). If the instance is deleted from the page, background threads may | |
23 * suddenly see their PP_Resource handles become invalid. In this case, calls | |
24 * will fail with PP_ERROR_BADRESOURCE. If you need to access data associated | |
25 * with your instance, you will probably want to create some kind of threadsafe | |
26 * proxy object that can handle asynchonous destruction of the instance object. | |
27 * | |
28 * Typical usage: | |
29 * On the main thread: | |
30 * - Create the thread yourself (using pthreads). | |
31 * - Create the message loop resource. | |
32 * - Pass the message loop resource to your thread's main function. | |
33 * - Call PostWork() on the message loop to run functions on the thread. | |
34 * | |
35 * From the background thread's main function: | |
36 * - Call AttachToCurrentThread() with the message loop resource. | |
37 * - Call Run() with the message loop resource. | |
38 * | |
39 * Your callacks should look like this: | |
40 * void DoMyWork(void* user_data, int32_t status) { | |
41 * if (status != PP_OK) { | |
42 * Cleanup(); // e.g. free user_data. | |
43 * return; | |
44 * } | |
45 * ... do your work... | |
46 * } | |
47 * For a C++ example, see ppapi/utility/threading/simple_thread.h | |
48 * | |
49 * (You can also create the message loop resource on the background thread, | |
50 * but then the main thread will have no reference to it should you want to | |
51 * call PostWork()). | |
52 * | |
53 * | |
54 * THREAD HANDLING | |
55 * | |
56 * The main thread has an implicitly created message loop. The main thread is | |
57 * the thread where PPP_InitializeModule and PPP_Instance functions are called. | |
58 * You can retrieve a reference to this message loop by calling | |
59 * GetForMainThread() or, if your code is on the main thread, | |
60 * GetForCurrentThread() will also work. | |
61 * | |
62 * Some special threads created by the system can not have message loops. In | |
63 * particular, the background thread created for audio processing has this | |
64 * requirement because it's intended to be highly responsive to keep up with | |
65 * the realtime requirements of audio processing. You can not make PPAPI calls | |
66 * from these threads. | |
67 * | |
68 * Once you associate a message loop with a thread, you don't have to keep a | |
69 * reference to it. The system will hold a reference to the message loop for as | |
70 * long as the thread is running. The current message loop can be retrieved | |
71 * using the GetCurrent() function. | |
72 * | |
73 * It is legal to create threads in your plugin without message loops, but | |
74 * PPAPI calls will fail unless explicitly noted in the documentation. | |
75 * | |
76 * You can create a message loop object on a thread and never actually run the | |
77 * message loop. This will allow you to call blocking PPAPI calls (via | |
78 * PP_BlockUntilComplete()). If you make any asynchronous calls, the callbacks | |
79 * from those calls will be queued in the message loop and never run. The same | |
80 * thing will happen if work is scheduled after the message loop exits and | |
81 * the message loop is not run again. | |
82 * | |
83 * | |
84 * DESTRUCTION AND ERROR HANDLING | |
85 * | |
86 * Often, your application will associate memory with completion callbacks. For | |
87 * example, the C++ CompletionCallbackFactory has a small amount of | |
88 * heap-allocated memory for each callback. This memory will be leaked if the | |
89 * callback is never run. To avoid this memory leak, you need to be careful | |
90 * about error handling and shutdown. | |
91 * | |
92 * There are a number of cases where posted callbacks will never be run: | |
93 * | |
94 * - You tear down the thread (via pthreads) without "destroying" the message | |
95 * loop (via PostQuit with should_destroy = PP_TRUE). In this case, any | |
96 * tasks in the message queue will be lost. | |
97 * | |
98 * - You create a message loop, post callbacks to it, and never run it. | |
99 * | |
100 * - You quit the message loop via PostQuit with should_destroy set to | |
101 * PP_FALSE. In this case, the system will assume the message loop will be | |
102 * run again later and keep your tasks. | |
103 * | |
104 * To do proper shutdown, call PostQuit with should_destroy = PP_TRUE. This | |
105 * will prohibit future work from being posted, and will allow the message loop | |
106 * to run until all pending tasks are run. | |
107 * | |
108 * If you post a callback to a message loop that's been destroyed, or to an | |
109 * invalid message loop, PostWork will return an error and will not run the | |
110 * callback. This is true even for callbacks with the "required" flag set, | |
111 * since the system may not even know what thread to issue the error callback | |
112 * on. | |
113 * | |
114 * Therefore, you should check for errors from PostWork and destroy any | |
115 * associated memory to avoid leaks. If you're using the C++ | |
116 * CompletionCallbackFactory, use the following pattern: | |
117 * | |
118 * pp::CompletionCallback callback = factory_.NewOptionalCallback(...); | |
119 * int32_t result = message_loop.PostWork(callback); | |
120 * if (result != PP_OK_COMPLETIONPENDING) | |
121 * callback.Run(result); | |
122 * | |
123 * This will run the callback with an error value, and assumes that the | |
124 * implementation of your callback checks the "result" argument and returns | |
125 * immediately on error. | |
126 */ | |
127 interface PPB_MessageLoop_Dev { | |
128 /** | |
129 * Creates a message loop resource. | |
130 * | |
131 * This may be called from any thread. After your thread starts but before | |
132 * issuing any other PPAPI calls on it, you must associate it with a message | |
133 * loop by calling AttachToCurrentThread. | |
134 */ | |
135 PP_Resource Create(PP_Instance instance); | |
136 | |
137 /** | |
138 * Returns a resource identifying the message loop for the main thread. The | |
139 * main thread always has a message loop created by the system. | |
140 */ | |
141 PP_Resource GetForMainThread(); | |
142 | |
143 /** | |
144 * Returns a reference to the PPB_MessageLoop object attached to the current | |
145 * thread. If there is no attached message loop, the return value will be 0. | |
146 */ | |
147 PP_Resource GetCurrent(); | |
148 | |
149 /** | |
150 * Sets the given message loop resource as being the associated message loop | |
151 * for the currently running thread. | |
152 * | |
153 * You must call this function exactly once on a thread before making any | |
154 * PPAPI calls. A message loop can only be attached to one thread, and the | |
155 * message loop can not be changed later. The message loop will be attached | |
156 * as long as the thread is running or until you quit with should_destroy | |
157 * set to PP_TRUE. | |
158 * | |
159 * If this function fails, attempting to run the message loop will fail. | |
160 * Note that you can still post work to the message loop: it will get queued | |
161 * up should the message loop eventually be successfully attached and run. | |
162 * | |
163 * @return | |
164 * - PP_OK: The message loop was successfully attached to the thread and is | |
165 * ready to use. | |
166 * - PP_ERROR_BADRESOURCE: The given message loop resource is invalid. | |
167 * - PP_ERROR_INPROGRESS: The current thread already has a message loop | |
168 * attached. This will always be the case for the main thread, which has | |
169 * an implicit system-created message loop attached. | |
170 * - PP_ERROR_WRONG_THREAD: The current thread type can not have a message | |
171 * loop attached to it. See the interface level discussion about these | |
172 * special threads, which include realtime audio threads. | |
173 */ | |
174 int32_t AttachToCurrentThread([in] PP_Resource message_loop); | |
175 | |
176 /** | |
177 * Runs the thread message loop. Running the message loop is required for you | |
178 * to get issued completion callbacks on the thread. | |
179 * | |
180 * The message loop identified by the argument must have been previously | |
181 * successfully attached to the current thread. | |
182 * | |
183 * You may not run nested message loops. Since the main thread has an | |
184 * implicit message loop that the system runs, you may not call Run on the | |
185 * main thread. | |
186 * | |
187 * @return | |
188 * - PP_OK: The message loop was successfully run. Note that on | |
189 * success, the message loop will only exit when you call PostQuit(). | |
190 * - PP_ERROR_BADRESOURCE: The given message loop resource is invalid. | |
191 * - PP_ERROR_WRONG_THREAD: You are attempting to run a message loop that | |
192 * has not been successfully attached to the current thread. Call | |
193 * AttachToCurrentThread(). | |
194 * - PP_ERROR_INPROGRESS: You are attempting to call Run in a nested | |
195 * fashion (Run is already on the stack). This will occur if you attempt | |
196 * to call run on the main thread's message loop (see above). | |
197 */ | |
198 int32_t Run([in] PP_Resource message_loop); | |
199 | |
200 /** | |
201 * Schedules work to run on the given message loop. This may be called from | |
202 * any thread. Posted work will be executed in the order it was posted when | |
203 * the message loop is Run(). | |
204 * | |
205 * @param message_loop The message loop resource. | |
206 * | |
207 * @param callback The completion callback to execute from the message loop. | |
208 * | |
209 * @param delay_ms The number of millseconds to delay execution of the given | |
210 * completion callback. Passing 0 means it will get queued normally and | |
211 * executed in order. | |
212 * | |
213 * | |
214 * The completion callback will be called with PP_OK as the "result" parameter | |
215 * if it is run normally. It is good practice to check for PP_OK and return | |
216 * early otherwise. | |
217 * | |
218 * The "required" flag on the completion callback is ignored. If there is an | |
219 * error posting your callback, the error will be returned from PostWork and | |
220 * the callback will never be run (because there is no appropriate place to | |
221 * run your callback with an error without causing unexpected threading | |
222 * problems). If you associate memory with the completion callback (for | |
223 * example, you're using the C++ CompletionCallbackFactory), you will need to | |
224 * free this or manually run the callback. See "Desctruction and error | |
225 * handling" above. | |
226 * | |
227 * | |
228 * You can call this function before the message loop has started and the | |
229 * work will get queued until the message loop is run. You can also post | |
230 * work after the message loop has exited as long as should_destroy was | |
231 * PP_FALSE. It will be queued until the next invocation of Run(). | |
232 * | |
233 * @return | |
234 * - PP_OK_COMPLETIONPENDING: The work was posted to the message loop's | |
235 * queue. As described above, this does not mean that the work has been | |
236 * or will be executed (if you never run the message loop after posting). | |
237 * - PP_ERROR_BADRESOURCE: The given message loop resource is invalid. | |
238 * - PP_ERROR_BADARGUMENT: The function pointer for the completion callback | |
239 * is null (this will be the case if you pass PP_BlockUntilComplete()). | |
240 * - PP_ERROR_FAILED: The message loop has been destroyed. | |
241 */ | |
242 int32_t PostWork([in] PP_Resource message_loop, | |
243 [in] PP_CompletionCallback callback, | |
244 [in] int64_t delay_ms); | |
245 | |
246 /** | |
247 * Posts a quit message to the given message loop's work queue. Work posted | |
248 * before that point will be processed before quitting. | |
249 * | |
250 * This may be called on the message loop registered for the current thread, | |
251 * or it may be called on the message loop registered for another thread. | |
252 * | |
253 * @param should_destroy Marks the message loop as being in a destroyed state | |
254 * and prevents further posting of messages. | |
255 * | |
256 * If you quit a message loop without setting should_destroy, it will still | |
257 * be attached to the thread and you can still run it again by calling Run() | |
258 * again. If you destroy it, it will be detached from the current thread. | |
259 * | |
260 * @return | |
261 * - PP_OK: The request to quit was successfully posted. | |
262 * - PP_ERROR_BADRESOURCE: The message loop was invalid. | |
263 * - PP_ERROR_WRONG_THREAD: You are attempting to quit the main thread. | |
264 * The main thread's message loop is managed by the system and can't be | |
265 * quit. | |
266 */ | |
267 int32_t PostQuit([in] PP_Resource message_loop, PP_Bool should_destroy); | |
268 }; | |
OLD | NEW |