Makes bindings work with nested message loops

mojo/public/cpp/bindings/message.h

Index: mojo/public/cpp/bindings/message.h
diff --git a/mojo/public/cpp/bindings/message.h b/mojo/public/cpp/bindings/message.h
index 10d10d0db3d1c5db295d097149eb0d338caec3cb..bfdabd140fa2a9d068254625d13f59c809d50a32 100644
--- a/mojo/public/cpp/bindings/message.h
+++ b/mojo/public/cpp/bindings/message.h
@@ -160,16 +160,14 @@ class MessageReceiverWithResponderStatus : public MessageReceiver {
       MOJO_WARN_UNUSED_RESULT = 0;
 };
 
-// Read a single message from the pipe and dispatch to the given receiver.  The
-// receiver may be null, in which case the message is simply discarded.
-// Returns MOJO_RESULT_SHOULD_WAIT if the caller should wait on the handle to
-// become readable. Returns MOJO_RESULT_OK if a message was dispatched and
-// otherwise returns an error code if something went wrong.
+// Read a single message from the pipe. The caller should have created the
+// Message, but not called Initialize(). Returns MOJO_RESULT_SHOULD_WAIT if
+// the caller should wait on the handle to become readable. Returns
+// MOJO_RESULT_OK if the message was read successfully and should be
+// dispatched, otherwise returns an error code if something went wrong.
 //
 // NOTE: The message hasn't been validated and may be malformed!
-MojoResult ReadAndDispatchMessage(MessagePipeHandle handle,
-                                  MessageReceiver* receiver,
-                                  bool* receiver_result);
+MojoResult ReadMessage(MessagePipeHandle handle, Message* message);
 
 }  // namespace mojo