Searched defs:AsyncWaiter (Results 1 - 4 of 4) sorted by relevance

/external/chromium_org/device/serial/
H A Dasync_waiter.h16 // result. If the AsyncWaiter is deleted before the handle is ready, the wait is
18 class AsyncWaiter { class in namespace:device
22 AsyncWaiter(mojo::Handle handle,
25 ~AsyncWaiter();
35 DISALLOW_COPY_AND_ASSIGN(AsyncWaiter);
H A Dasync_waiter.cc9 AsyncWaiter::AsyncWaiter(mojo::Handle handle, function in class:device::AsyncWaiter
18 &AsyncWaiter::WaitComplete,
22 AsyncWaiter::~AsyncWaiter() {
28 void AsyncWaiter::WaitComplete(void* waiter, MojoResult result) {
29 static_cast<AsyncWaiter*>(waiter)->WaitCompleteInternal(result);
32 void AsyncWaiter::WaitCompleteInternal(MojoResult result) {
/external/chromium_org/mojo/public/java/system/src/org/chromium/mojo/system/
H A DAsyncWaiter.java10 * A class which implements the {@link AsyncWaiter} allows asynchronously waiting on a background
13 public interface AsyncWaiter { interface
23 * Must be called from the same thread as {@link AsyncWaiter#asyncWait} was called from.
29 * Callback passed to {@link AsyncWaiter#asyncWait}.
/external/chromium_org/base/synchronization/
H A Dwaitable_event_watcher_posix.cc18 // The basic design is that we add an AsyncWaiter to the wait-list of the event.
19 // That AsyncWaiter has a pointer to MessageLoop, and a Task to be posted to it.
57 // fired. An AsyncWaiter may only be in a single wait-list.
59 class AsyncWaiter : public WaitableEvent::Waiter { class in namespace:base
61 AsyncWaiter(MessageLoop* message_loop, function in class:base::AsyncWaiter
78 // We can always return true because an AsyncWaiter is never in two
171 waiter_ = new AsyncWaiter(current_ml, internal_callback_, cancel_flag_.get());
214 // pointer values then it's possible that the AsyncWaiter could have been
217 // AsyncWaiter and remove it.

Completed in 117 milliseconds