[go: nahoru, domu]

tree: b9138d8e7fb33c5a766b88fb63630d3b7c755ddb [path history] [tgz]
  1. BUILD.gn
  2. DEPS
  3. DIR_METADATA
  4. event_trace_logging_platform.cc
  5. event_trace_logging_platform.h
  6. logging.cc
  7. message_port_tls_connection.cc
  8. message_port_tls_connection.h
  9. message_port_tls_connection_unittest.cc
  10. net_udp_socket.cc
  11. net_udp_socket.h
  12. network_context.cc
  13. network_context.h
  14. network_util.cc
  15. network_util.h
  16. OWNERS
  17. README.md
  18. task_runner.cc
  19. task_runner.h
  20. time.cc
  21. tls_client_connection.cc
  22. tls_client_connection.h
  23. tls_client_connection_unittest.cc
  24. tls_connection_factory.cc
  25. tls_connection_factory.h
  26. tls_connection_factory_unittest.cc
  27. trace_logging_platform.cc
  28. udp_socket.cc
  29. udp_socket.h
components/openscreen_platform/README.md

This directory contains an implementation of the Open Screen platform API along with utility functions, using the //base and //net directories in Chromium.

Any Chromium target that (indirectly) depends on //third_party/openscreen/src/platform:api must also (indirectly) depend on one of two components provided by this component. In nearly all cases, the dependency should be in the same deps as //third_party/openscreen/src/platform:api. Most external targets should depend on //components/openscreen_platform. Targets that cannot use the Network Service should instead depend on //components/openscreen_platform:openscreen_platform_using_net_sockets, which uses a //net-based implementation of UdpSocket. These two targets are incompatible with each other.

A very small set of intermediary targets that are used by both types of targets above depend directly on //components/openscreen_platform:openscreen_platform_without_sockets and push the requirement to depend on one of the two public targets up to the dependency chain.