Rebecca Chang Swee Fun 213e2ca447 Publish chromium based on 102.0.5005.115 1 year ago
..
client 213e2ca447 Publish chromium based on 102.0.5005.115 1 year ago
compression 213e2ca447 Publish chromium based on 102.0.5005.115 1 year ago
encryption 213e2ca447 Publish chromium based on 102.0.5005.115 1 year ago
metrics 213e2ca447 Publish chromium based on 102.0.5005.115 1 year ago
proto 213e2ca447 Publish chromium based on 102.0.5005.115 1 year ago
resources 213e2ca447 Publish chromium based on 102.0.5005.115 1 year ago
storage 213e2ca447 Publish chromium based on 102.0.5005.115 1 year ago
storage_selector 213e2ca447 Publish chromium based on 102.0.5005.115 1 year ago
util 213e2ca447 Publish chromium based on 102.0.5005.115 1 year ago
DIR_METADATA 213e2ca447 Publish chromium based on 102.0.5005.115 1 year ago
OWNERS 213e2ca447 Publish chromium based on 102.0.5005.115 1 year ago
README.md 213e2ca447 Publish chromium based on 102.0.5005.115 1 year ago

README.md

The Encrypted Reporting Pipeline (ERP) provides a universal method for upload of data for enterprise customers.

The code structure looks like this: Chrome:

  • //components/reporting Code shared between Chrome and Chrome OS.
  • //chrome/browser/policy/messaging_layer Code that lives only in the browser, primary interfaces for reporting data such as ReportQueueImpl and ReportQueueConfiguration. Chrome OS:
  • //platform2/missived Daemon for encryption and storage of reports.

If you’d like to begin using ERP within Chrome please check the comment in //components/reporting/client/report_queue_provider.h.