HomeSort by relevance Sort by last modified time
    Searched full:completioncallback (Results 551 - 575 of 806) sorted by null

<<21222324252627282930>>

  /external/chromium_org/third_party/WebKit/public/web/
WebSpellCheckClient.h 68 WebTextCheckingCompletion* completionCallback) { }
  /external/chromium_org/third_party/skia/platform_tools/nacl/src/
nacl_hello.cpp 77 fDeviceContext.Flush(pp::CompletionCallback(&FlushCallback, this));
  /external/skia/platform_tools/nacl/src/
nacl_hello.cpp 77 fDeviceContext.Flush(pp::CompletionCallback(&FlushCallback, this));
  /external/chromium_org/chrome/browser/spellchecker/
spellcheck_platform_mac_unittest.cc 19 : callback_(base::Bind(&SpellcheckMacTest::CompletionCallback,
37 void CompletionCallback(const std::vector<SpellCheckResult>& results) {
  /external/chromium_org/chrome/test/chromedriver/net/
websocket.cc 70 void WebSocket::Connect(const net::CompletionCallback& callback) {
250 net::CompletionCallback temp = connect_callback_;
  /external/chromium_org/content/browser/
database_quota_client_unittest.cc 75 const net::CompletionCallback& callback) OVERRIDE {
87 void AsyncDeleteDataForOrigin(const net::CompletionCallback& callback) {
  /external/chromium_org/media/cdm/ppapi/
cdm_file_io_impl.h 54 const pp::CompletionCallback& first_file_read_cb);
203 pp::CompletionCallback first_file_read_cb_;
  /external/chromium_org/native_client_sdk/doc_generated/pepper_beta/cpp/
classpp_1_1_message_loop.html 30 <tr><td class="memItemLeft" align="right" valign="top">int32_t&#160;</td><td class="memItemRight" valign="bottom"><a class="el" href="classpp_1_1_message_loop.html#a2c24506ef8be1745d29983b2d7803e36">PostWork</a> (const <a class="el" href="classpp_1_1_completion_callback.html">CompletionCallback</a> &amp;callback, int64_t delay_ms=0)</td></tr>
71 <p>Often, your application will associate memory with completion callbacks. For example, the C++ <a class="el" href="classpp_1_1_completion_callback_factory.html" title="CompletionCallbackFactory&lt;T&gt; may be used to create CompletionCallback objects that are bound to membe...">CompletionCallbackFactory</a> has a small amount of heap-allocated memory for each callback. This memory will be leaked if the callback is never run. To avoid this memory leak, you need to be careful about error handling and shutdown.</p>
84 <p>Therefore, you should check for errors from PostWork and destroy any associated memory to avoid leaks. If you're using the C++ <a class="el" href="classpp_1_1_completion_callback_factory.html" title="CompletionCallbackFactory&lt;T&gt; may be used to create CompletionCallback objects that are bound to membe...">CompletionCallbackFactory</a>, use the following pattern: </p>
85 <div class="fragment"><pre class="fragment"> <a class="code" href="classpp_1_1_completion_callback.html" title="This API enables you to implement and receive callbacks when Pepper operations complete asynchronousl...">pp::CompletionCallback</a> callback = factory_.NewOptionalCallback(...);
88 callback.<a class="code" href="classpp_1_1_completion_callback.html#a7795404cc15a4f96523c28db21d364c4" title="Run() is used to run the CompletionCallback.">Run</a>(result);
247 <a class="anchor" id="a2c24506ef8be1745d29983b2d7803e36"></a><!-- doxytag: member="pp::MessageLoop::PostWork" ref="a2c24506ef8be1745d29983b2d7803e36" args="(const CompletionCallback &amp;callback, int64_t delay_ms=0)" -->
254 <td class="paramtype">const <a class="el" href="classpp_1_1_completion_callback.html">CompletionCallback</a> &amp;&#160;</td>
281 <p>The "required" flag on the completion callback is ignored. If there is an error posting your callback, the error will be returned from PostWork and the callback will never be run (because there is no appropriate place to run your callback with an error without causing unexpected threading problems). If you associate memory with the completion callback (for example, you're using the C++ <a class="el" href="classpp_1_1_completion_callback_factory.html" title="CompletionCallbackFactory&lt;T&gt; may be used to create CompletionCallback objects that are bound to membe...">CompletionCallbackFactory</a>), you will need to free this or manually run the callback. See "Desctruction and error
  /external/chromium_org/native_client_sdk/doc_generated/pepper_dev/cpp/
classpp_1_1_message_loop.html 30 <tr><td class="memItemLeft" align="right" valign="top">int32_t&#160;</td><td class="memItemRight" valign="bottom"><a class="el" href="classpp_1_1_message_loop.html#a2c24506ef8be1745d29983b2d7803e36">PostWork</a> (const <a class="el" href="classpp_1_1_completion_callback.html">CompletionCallback</a> &amp;callback, int64_t delay_ms=0)</td></tr>
71 <p>Often, your application will associate memory with completion callbacks. For example, the C++ <a class="el" href="classpp_1_1_completion_callback_factory.html" title="CompletionCallbackFactory&lt;T&gt; may be used to create CompletionCallback objects that are bound to membe...">CompletionCallbackFactory</a> has a small amount of heap-allocated memory for each callback. This memory will be leaked if the callback is never run. To avoid this memory leak, you need to be careful about error handling and shutdown.</p>
84 <p>Therefore, you should check for errors from PostWork and destroy any associated memory to avoid leaks. If you're using the C++ <a class="el" href="classpp_1_1_completion_callback_factory.html" title="CompletionCallbackFactory&lt;T&gt; may be used to create CompletionCallback objects that are bound to membe...">CompletionCallbackFactory</a>, use the following pattern: </p>
85 <div class="fragment"><pre class="fragment"> <a class="code" href="classpp_1_1_completion_callback.html" title="This API enables you to implement and receive callbacks when Pepper operations complete asynchronousl...">pp::CompletionCallback</a> callback = factory_.NewOptionalCallback(...);
88 callback.<a class="code" href="classpp_1_1_completion_callback.html#a7795404cc15a4f96523c28db21d364c4" title="Run() is used to run the CompletionCallback.">Run</a>(result);
247 <a class="anchor" id="a2c24506ef8be1745d29983b2d7803e36"></a><!-- doxytag: member="pp::MessageLoop::PostWork" ref="a2c24506ef8be1745d29983b2d7803e36" args="(const CompletionCallback &amp;callback, int64_t delay_ms=0)" -->
254 <td class="paramtype">const <a class="el" href="classpp_1_1_completion_callback.html">CompletionCallback</a> &amp;&#160;</td>
281 <p>The "required" flag on the completion callback is ignored. If there is an error posting your callback, the error will be returned from PostWork and the callback will never be run (because there is no appropriate place to run your callback with an error without causing unexpected threading problems). If you associate memory with the completion callback (for example, you're using the C++ <a class="el" href="classpp_1_1_completion_callback_factory.html" title="CompletionCallbackFactory&lt;T&gt; may be used to create CompletionCallback objects that are bound to membe...">CompletionCallbackFactory</a>), you will need to free this or manually run the callback. See "Desctruction and error
  /external/chromium_org/native_client_sdk/doc_generated/pepper_stable/cpp/
classpp_1_1_message_loop.html 30 <tr><td class="memItemLeft" align="right" valign="top">int32_t&#160;</td><td class="memItemRight" valign="bottom"><a class="el" href="classpp_1_1_message_loop.html#a2c24506ef8be1745d29983b2d7803e36">PostWork</a> (const <a class="el" href="classpp_1_1_completion_callback.html">CompletionCallback</a> &amp;callback, int64_t delay_ms=0)</td></tr>
71 <p>Often, your application will associate memory with completion callbacks. For example, the C++ <a class="el" href="classpp_1_1_completion_callback_factory.html" title="CompletionCallbackFactory&lt;T&gt; may be used to create CompletionCallback objects that are bound to membe...">CompletionCallbackFactory</a> has a small amount of heap-allocated memory for each callback. This memory will be leaked if the callback is never run. To avoid this memory leak, you need to be careful about error handling and shutdown.</p>
84 <p>Therefore, you should check for errors from PostWork and destroy any associated memory to avoid leaks. If you're using the C++ <a class="el" href="classpp_1_1_completion_callback_factory.html" title="CompletionCallbackFactory&lt;T&gt; may be used to create CompletionCallback objects that are bound to membe...">CompletionCallbackFactory</a>, use the following pattern: </p>
85 <div class="fragment"><pre class="fragment"> <a class="code" href="classpp_1_1_completion_callback.html" title="This API enables you to implement and receive callbacks when Pepper operations complete asynchronousl...">pp::CompletionCallback</a> callback = factory_.NewOptionalCallback(...);
88 callback.<a class="code" href="classpp_1_1_completion_callback.html#a7795404cc15a4f96523c28db21d364c4" title="Run() is used to run the CompletionCallback.">Run</a>(result);
247 <a class="anchor" id="a2c24506ef8be1745d29983b2d7803e36"></a><!-- doxytag: member="pp::MessageLoop::PostWork" ref="a2c24506ef8be1745d29983b2d7803e36" args="(const CompletionCallback &amp;callback, int64_t delay_ms=0)" -->
254 <td class="paramtype">const <a class="el" href="classpp_1_1_completion_callback.html">CompletionCallback</a> &amp;&#160;</td>
281 <p>The "required" flag on the completion callback is ignored. If there is an error posting your callback, the error will be returned from PostWork and the callback will never be run (because there is no appropriate place to run your callback with an error without causing unexpected threading problems). If you associate memory with the completion callback (for example, you're using the C++ <a class="el" href="classpp_1_1_completion_callback_factory.html" title="CompletionCallbackFactory&lt;T&gt; may be used to create CompletionCallback objects that are bound to membe...">CompletionCallbackFactory</a>), you will need to free this or manually run the callback. See "Desctruction and error
  /external/chromium_org/net/dns/
mock_host_resolver.h 80 const CompletionCallback& callback,
229 const CompletionCallback& callback,
  /external/chromium_org/net/proxy/
dhcp_proxy_script_adapter_fetcher_win.cc 49 const std::string& adapter_name, const CompletionCallback& callback) {
187 CompletionCallback callback = callback_;
dhcp_proxy_script_fetcher_win.cc 77 const CompletionCallback& callback) {
251 CompletionCallback callback = callback_;
  /external/chromium_org/net/quic/
quic_stream_factory.h 62 const CompletionCallback& callback);
79 CompletionCallback callback_;
  /external/chromium_org/net/socket/
client_socket_pool.h 104 const CompletionCallback& callback,
124 // RequestSocket call being cancelled. The associated CompletionCallback is
ssl_client_socket_unittest.cc 63 virtual int Connect(const CompletionCallback& callback) OVERRIDE {
107 const CompletionCallback& callback) OVERRIDE {
112 const CompletionCallback& callback) OVERRIDE {
140 const CompletionCallback& callback) OVERRIDE;
168 CompletionCallback user_read_callback_;
185 const CompletionCallback& callback) {
270 const CompletionCallback& callback) OVERRIDE;
273 const CompletionCallback& callback) OVERRIDE;
315 const CompletionCallback& callback) {
323 const CompletionCallback& callback)
    [all...]
  /external/chromium_org/net/socket_stream/
socket_stream_unittest.cc 60 explicit SocketStreamEventRecorder(const CompletionCallback& callback)
93 const CompletionCallback& callback) OVERRIDE {
184 const CompletionCallback callback_;
185 CompletionCallback connection_callback_;
195 explicit SelfDeletingDelegate(const CompletionCallback& callback)
204 CompletionCallback callback = callback_;
234 const CompletionCallback callback_;
257 const CompletionCallback& callback) OVERRIDE {
    [all...]
  /external/chromium_org/net/websockets/
websocket_stream.h 158 const CompletionCallback& callback) = 0;
175 const CompletionCallback& callback) = 0;
  /external/chromium_org/remoting/client/plugin/
pepper_port_allocator.cc 134 pp::CompletionCallback callback =
168 pp::CompletionCallback callback = callback_factory_.NewCallback(
  /external/chromium_org/chrome/browser/net/
chrome_network_delegate.cc 107 const net::CompletionCallback& callback,
357 const net::CompletionCallback& callback,
413 net::CompletionCallback wrapped_callback = callback;
457 const net::CompletionCallback& callback,
486 const net::CompletionCallback& callback,
803 const net::CompletionCallback& callback) {
  /external/chromium_org/extensions/browser/api/cast_channel/
cast_socket.cc 184 void CastSocket::Connect(const net::CompletionCallback& callback) {
418 void CastSocket::Close(const net::CompletionCallback& callback) {
457 net::CompletionCallback& callback = write_queue_.front().callback;
464 const net::CompletionCallback& callback) {
488 const net::CompletionCallback& callback) {
863 CastSocket::WriteRequest::WriteRequest(const net::CompletionCallback& callback)
cast_transport_unittest.cc 65 void Push(const net::CompletionCallback& cb) { cb_queue_.push(cb); }
74 std::queue<net::CompletionCallback> cb_queue_;
104 // buf_idx (template parameter 0): 0-based index of the CompletionCallback.
160 const net::CompletionCallback& callback));
164 const net::CompletionCallback& callback));
  /external/chromium_org/storage/browser/database/
database_tracker.cc 182 net::CompletionCallback());
233 net::CompletionCallback cb = callback->first;
633 const net::CompletionCallback& callback) {
648 const net::CompletionCallback& callback) {
668 const net::CompletionCallback& callback) {
718 const std::string& origin, const net::CompletionCallback& callback) {
  /external/chromium_org/net/http/
http_cache.cc 86 const CompletionCallback& callback) {
126 CompletionCallback callback; // BackendCallback.
150 const net::CompletionCallback& cb, disk_cache::Backend** backend)
190 net::CompletionCallback callback_; // User callback.
384 const CompletionCallback& callback) {
418 CreateBackend(NULL, net::CompletionCallback());
464 CreateBackend(NULL, net::CompletionCallback());
495 const net::CompletionCallback& callback) {
537 WI_CREATE_BACKEND, trans, net::CompletionCallback(), NULL);
    [all...]
  /external/chromium_org/google_apis/drive/
base_requests.cc 131 int ResponseWriter::Initialize(const net::CompletionCallback& callback) {
141 const net::CompletionCallback& callback) {
155 DidWrite(buffer, net::CompletionCallback(), result);
163 int ResponseWriter::Finish(const net::CompletionCallback& callback) {
171 const net::CompletionCallback& callback,

Completed in 488 milliseconds

<<21222324252627282930>>