dom/webbrowserpersist/PWebBrowserPersistSerialize.ipdl
author Narcis Beleuzu <nbeleuzu@mozilla.com>
Sun, 29 Jul 2018 03:55:23 +0300
changeset 483986 aaee68beff800bcf076d9c49b5c1f6531b135579
parent 374209 58c050e010a596a5cbb419472714d2d68b8906c2
permissions -rw-r--r--
Backed out 2 changesets (bug 1463016, bug 1463291) for geckoview failures Backed out changeset fcfb99baa0f0 (bug 1463291) Backed out changeset 0d69b4fb1ed4 (bug 1463016)

/* -*- Mode: IDL; tab-width: 8; indent-tabs-mode: nil; c-basic-offset: 2 -*- */
/* 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 PWebBrowserPersistDocument;

namespace mozilla {

// This actor represents both an nsIWebBrowserPersistWriteCompletion
// and the nsIOutputStream passed with it to the writeContent method.
protocol PWebBrowserPersistSerialize {
  manager PWebBrowserPersistDocument;

parent:
  // This sends the data with no flow control, so the parent could
  // wind up buffering an arbitrarily large amount of data...  but
  // it's a serialized DOM that's already in memory as DOM nodes, so
  // this is at worst just a constant-factor increase in memory usage.
  // Also, Chromium does the same thing; see
  // content::RenderViewImpl::didSerializeDataForFrame.
  async WriteData(uint8_t[] aData);

  // This is the onFinish method.
  async __delete__(nsCString aContentType,
                   nsresult aStatus);
};

} // namespace mozilla