Much network service code is currently in content (specifically in content/public/{common,network}, content/network). Most of it is not dependent on other efforts and can be migrated to //services/network. "Wrapper" code that needs to be called directly can be placed in //services/network/public/cpp. All interfaces can be placed in //services/network/public/interfaces--that does not interfere with either their use or generation from content code.
The major blockers for this effort are data types that the Mojo interfaces in content depend on. A very incomplete list includes:
* SSLInfo (uses IPC serialization/de-serializatino)
* resource_request_body, whichhas a dependence on storage/common/data_element.h and tentatively relies on some blog code.
* ResourceResponseHead uses previosu and dev tools.
Much network service code is currently in content (specifically in content/public/{common,network}, content/network). Most of it is not dependent on other efforts and can be migrated to //services/network. "Wrapper" code that needs to be called directly can be placed in //services/network/public/cpp. All interfaces can be placed in //services/network/public/interfaces--that does not interfere with either their use or generation from content code.
The major blockers for this effort are data types that the Mojo interfaces in content depend on. A very incomplete list includes:
* SSLInfo (uses IPC serialization/de-serializatino)
* resource_request_body, which has a dependence on storage/common/data_element.h and tentatively relies on some blog code.
* ResourceResponseHead uses previews and dev tools.
Comment 1 by jam@chromium.org
, Nov 15 2017