| OLD | NEW |
| 1 Chrome Platform Services | 1 Chrome Platform Services |
| 2 ==== | 2 ==== |
| 3 | 3 |
| 4 ### Overview | 4 ### Overview |
| 5 | 5 |
| 6 This directory contains Chrome Platform Services. If you think of Chrome as a | 6 This directory contains Chrome Platform Services. If you think of Chrome as a |
| 7 "portable OS," Chrome Platform Services can be thought of as that OS' "system | 7 "portable OS," Chrome Platform Services can be thought of as that OS' "system |
| 8 services". | 8 services". |
| 9 | 9 |
| 10 Roughly each subdirectory here corresponds to a service that: | 10 Roughly each subdirectory here corresponds to a service that: |
| (...skipping 18 matching lines...) Expand all Loading... |
| 29 | 29 |
| 30 Service code should also take care to tightly limit the dependencies on static | 30 Service code should also take care to tightly limit the dependencies on static |
| 31 libraries from outside of `//services`. Dependencies to large platform | 31 libraries from outside of `//services`. Dependencies to large platform |
| 32 layers like `//content`, `//chrome` or `//third_party/WebKit` must be avoided. | 32 layers like `//content`, `//chrome` or `//third_party/WebKit` must be avoided. |
| 33 | 33 |
| 34 ### Physical Packaging | 34 ### Physical Packaging |
| 35 | 35 |
| 36 Note that while it may be possible to build a discrete physical package (DSO) | 36 Note that while it may be possible to build a discrete physical package (DSO) |
| 37 for each service, products consuming these services may package them | 37 for each service, products consuming these services may package them |
| 38 differently, e.g. by combining them into a single package. | 38 differently, e.g. by combining them into a single package. |
| 39 |
| 40 ### High-level Design Doc |
| 41 https://docs.google.com/document/d/15I7sQyQo6zsqXVNAlVd520tdGaS8FCicZHrN0yRu-oU/
edit#heading=h.p37l9e7o0io5 |
| OLD | NEW |