ffd09bcb7e
MessagePortCastCore bridges MessagePortCore, which supports a Connector allowing an arbitrary transport layer between ports. By default a pair will talk directly. This is intended for use on platforms that do not use FIDL or Mojo but wish to use Cast bindings. MessagePortCore extends from cast_message_port::MessagePort to support multiple types of TaskRunners. There is a case where we might need multiple implementations, so this should stay for now but can be revisted later. Additionally, visibility restrictions of the headers have been removed so other components may reuse the abstraction. CreatePair has been moved so multiple implementations of MessagePort may be linked. CreatePair currently always creates the MessagePort "platform" type which can communicate with bindings. Bug: None Change-Id: I61061875e2487568c2d55d043bbefab55e5f94be Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2956392 Reviewed-by: Sean Topping <seantopping@chromium.org> Reviewed-by: Jiawei Li <lijiawei@chromium.org> Reviewed-by: Ryan Keane <rwkeane@google.com> Reviewed-by: Kevin Marshall <kmarshall@chromium.org> Commit-Queue: Shawn Quereshi <shawnq@google.com> Cr-Commit-Position: refs/heads/master@{#894442}
Cast base
cast_features
This file contains tools for checking the feature state of all of the features which affect Cast products. Cast features build upon the Chrome feature system. Some aspects of Cast require the feature system to work differently, however, so some additional logic has been layered on top. Details are available in comments of the header file. The basics are:
- If you are adding a new feature, add it to
cast_features.ccso it lives alongside existing features - Add your new feature to the list of
kFeaturesincast_features.cc
const base::Feature kMyFeature{"my_feature", base::FEATURE_DISABLED_BY_DEFAULT};
const base::Feature* kFeatures[] = {
// ..other features
&kMyFeature
}