* payload view) is modified.
*
* While a payload view does not allow users to modify the underlying bytes
* payload view) is modified.
*
* While a payload view does not allow users to modify the underlying bytes
- * of the payload, it can be used to 'pop' file descriptors using an iterator
- * belonging to the top-level payload view.
+ * of the payload, it can be used to 'pop' file descriptor handles using an
+ * iterator belonging to the top-level payload view.
- * an implicit file descriptor iterator. Any payload view created from another
- * payload view will share the same underlying file descriptor iterator.
+ * an implicit file descriptor handle iterator. Any payload view created from
+ * another payload view will share the same underlying file descriptor handle
+ * iterator.
- * The rationale for this is that a payload is never consumed directly, it
- * must be consumed through a payload view.
+ * The rationale for this is that a payload is never consumed directly, it must
+ * be consumed through a payload view.
*
* Typically, a payload view will be used to rebuild a previously serialized
* object hierarchy. Sharing an underlying iterator allows aggregate objects
* to provide a restricted view of the payload to their members, which will
*
* Typically, a payload view will be used to rebuild a previously serialized
* object hierarchy. Sharing an underlying iterator allows aggregate objects
* to provide a restricted view of the payload to their members, which will
- * Pop an fd from a payload view.
- * No ownership of the file descriptor is assumed by the payload.
+ * Pop an fd handle from a payload view.
+ *
+ * A reference to the returned fd_handle is acquired on behalf of the caller.