Split PostMessageHandler from PostMessageServiceConnection
Stop inheriting from it and instead use the two classes separately, with PostMessageServiceConnection abstracted out of PostMessageHandler behind the PostMessageBackend interface added in change 1299016. This means we now store a PostMessageServiceConnection in SessionParams and call to it instead of PostMessageHandler for behaviour relating to the service connection. The result of this change is that PostMessageHandler can be used without a service connection, allowing us to use it directly from CustomTabActivity in a future CL. Bug: 898840 Change-Id: Ifd06ee0a803ecd82c350d7b5466bf0a0ee35440b Reviewed-on: https://chromium-review.googlesource.com/c/1299143 Commit-Queue: David Barker <barkerd@google.com> Reviewed-by:Michael van Ouwerkerk <mvanouwerkerk@chromium.org> Reviewed-by:
Peter Conn <peconn@chromium.org> Cr-Commit-Position: refs/heads/master@{#603516}
Showing
Please register or sign in to comment