Adding upstream version 86.0.1.upstream/86.0.1upstream

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

1 files changed, 46 insertions, 0 deletions

diff --git a/dom/file/ipc/PRemoteLazyInputStream.ipdl b/dom/file/ipc/PRemoteLazyInputStream.ipdl
new file mode 100644
index 0000000000..a2bc3a5ca2
--- /dev/null
+++ b/dom/file/ipc/PRemoteLazyInputStream.ipdl
@@ -0,0 +1,46 @@
+/* This Source Code Form is subject to the terms of the Mozilla Public
+ * License, v. 2.0. If a copy of the MPL was not distributed with this file,
+ * You can obtain one at http://mozilla.org/MPL/2.0/. */
+
+include protocol PBackground;
+include protocol PChildToParentStream;
+include protocol PContent;
+include protocol PFileDescriptorSet;
+include protocol PParentToChildStream;
+include protocol PSocketProcess;
+
+include IPCStream;
+
+namespace mozilla {
+
+refcounted protocol PRemoteLazyInputStream
+{
+  manager PBackground or PContent or PSocketProcess;
+
+parent:
+  async StreamNeeded();
+
+  async LengthNeeded();
+
+  // When this is called, the parent releases the inputStream and sends a
+  // __delete__.
+  async Close();
+
+child:
+  async StreamReady(IPCStream? aStream);
+
+  async LengthReady(int64_t aLength);
+
+both:
+  // __delete__ can be called by parent and by child for 2 reasons:
+  // - parent->child: This happens after a Close(). The child wants to inform
+  //                  the parent that no other messages will be dispatched and
+  //                  that the channel can be interrupted.
+  // - child->parent: before any operation, the child could start a migration
+  //                  from the current thread to a dedicated DOM-File one. The
+  //                  reason why a __delete__ is sent from child to parent is
+  //                  because it doesn't require any additional runnables.
+  async __delete__();
+};
+
+} // namespace mozilla