tree: c7040673fbfa7bd47eaa9b2c86f6852a19911476 [path history] [tgz]
  1. public/
  2. auction_downloader.cc
  3. auction_downloader.h
  4. auction_downloader_unittest.cc
  5. auction_v8_helper.cc
  6. auction_v8_helper.h
  7. auction_v8_helper_unittest.cc
  8. auction_worklet_service_impl.cc
  9. auction_worklet_service_impl.h
  10. bidder_worklet.cc
  11. bidder_worklet.h
  12. bidder_worklet_unittest.cc
  13. BUILD.gn
  14. console.cc
  15. console.h
  16. DEPS
  17. DIR_METADATA
  18. OWNERS
  19. README.md
  20. report_bindings.cc
  21. report_bindings.h
  22. seller_worklet.cc
  23. seller_worklet.h
  24. seller_worklet_unittest.cc
  25. trusted_bidding_signals.cc
  26. trusted_bidding_signals.h
  27. trusted_bidding_signals_unittest.cc
  28. worklet_loader.cc
  29. worklet_loader.h
  30. worklet_loader_unittest.cc
  31. worklet_test_util.cc
  32. worklet_test_util.h
content/services/auction_worklet/README.md

Auction Worklet Service

A central part of FLEDGE‘s running of on-device ad auctions is the execution of bidding and bid scoring worklets. These worklets execute JavaScript functions that do not have access to networking, storage, or any other part of a web page (e.g. DOM). Due to the execution of downloaded code and these isolation requirements they’re run in a separate process. The Auction Worklet Service orchestrates and controls the execution of these auction worklets. Before making changes to this service please thoroughly consult the OWNERS to ensure changes do not violate the isolation requirements.