Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(8)

Unified Diff: mojo/public/java/src/org/chromium/mojo/system/MessagePipeHandle.java

Issue 325953006: Add pass operation on handles. (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src
Patch Set: Fix findbugs issue Created 6 years, 6 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: mojo/public/java/src/org/chromium/mojo/system/MessagePipeHandle.java
diff --git a/mojo/public/java/src/org/chromium/mojo/system/MessagePipeHandle.java b/mojo/public/java/src/org/chromium/mojo/system/MessagePipeHandle.java
index 086f6267df3a9983ce628d4b82ce3f0f7c9b5e42..cfb032756e93b91a6e57dce93f46f7e48365f83d 100644
--- a/mojo/public/java/src/org/chromium/mojo/system/MessagePipeHandle.java
+++ b/mojo/public/java/src/org/chromium/mojo/system/MessagePipeHandle.java
@@ -83,18 +83,6 @@ public interface MessagePipeHandle extends Handle {
}
/**
- * Writes a message to the message pipe endpoint, with message data specified by |bytes| and
- * attached handles specified by |handles|, and options specified by |flags|. If there is no
- * message data, |bytes| may be null, otherwise it must be a direct ByteBuffer. If there are no
- * attached handles, |handles| may be null.
- * <p>
- * If handles are attached, on success the handles will no longer be valid (the receiver will
- * receive equivalent, but logically different, handles). Handles to be sent should not be in
- * simultaneous use (e.g., on another thread).
- */
- void writeMessage(ByteBuffer bytes, List<? extends Handle> handles, WriteFlags flags);
-
- /**
* Result of the |readMessage| method.
*/
public static class ReadMessageResult {
@@ -175,6 +163,24 @@ public interface MessagePipeHandle extends Handle {
}
/**
+ * @see org.chromium.mojo.system.Handle#pass()
+ */
+ @Override
+ public MessagePipeHandle pass();
+
+ /**
+ * Writes a message to the message pipe endpoint, with message data specified by |bytes| and
+ * attached handles specified by |handles|, and options specified by |flags|. If there is no
+ * message data, |bytes| may be null, otherwise it must be a direct ByteBuffer. If there are no
+ * attached handles, |handles| may be null.
+ * <p>
+ * If handles are attached, on success the handles will no longer be valid (the receiver will
+ * receive equivalent, but logically different, handles). Handles to be sent should not be in
+ * simultaneous use (e.g., on another thread).
+ */
+ void writeMessage(ByteBuffer bytes, List<? extends Handle> handles, WriteFlags flags);
+
+ /**
* Reads a message from the message pipe endpoint; also usable to query the size of the next
* message or discard the next message. |bytes| indicate the buffer/buffer size to receive the
* message data (if any) and |maxNumberOfHandles| indicate the maximum handle count to receive

Powered by Google App Engine
This is Rietveld 408576698