Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(333)

Side by Side Diff: services/README.md

Issue 2849463006: Add documentation on servicification recipes (Closed)
Patch Set: Response to reviews Created 3 years, 7 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
« no previous file with comments | « docs/servicification.md ('k') | no next file » | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
1 # Chrome Foundation Services 1 # Chrome Foundation Services
2 2
3 [TOC] 3 [TOC]
4 4
5 ## Overview 5 ## Overview
6 6
7 This directory contains Chrome Foundation Services. If you think of Chrome as a 7 This directory contains Chrome Foundation Services. If you think of Chrome as a
8 "portable OS," Chrome Foundation Services can be thought of as that OS' 8 "portable OS," Chrome Foundation Services can be thought of as that OS'
9 foundational "system services" layer. 9 foundational "system services" layer.
10 10
(...skipping 28 matching lines...) Expand all
39 Note that while it may be possible to build a discrete physical package (DSO) 39 Note that while it may be possible to build a discrete physical package (DSO)
40 for each service, products consuming these services may package them 40 for each service, products consuming these services may package them
41 differently, e.g. by combining them into a single package. 41 differently, e.g. by combining them into a single package.
42 42
43 ## Additional Documentation 43 ## Additional Documentation
44 44
45 [High-level Design Doc](https://docs.google.com/document/d/15I7sQyQo6zsqXVNAlVd5 20tdGaS8FCicZHrN0yRu-oU) 45 [High-level Design Doc](https://docs.google.com/document/d/15I7sQyQo6zsqXVNAlVd5 20tdGaS8FCicZHrN0yRu-oU)
46 46
47 [Servicification Homepage](https://sites.google.com/a/chromium.org/dev/servicifi cation) 47 [Servicification Homepage](https://sites.google.com/a/chromium.org/dev/servicifi cation)
48 48
49 [Servicification Strategies](docs/servicification.md)
50
49 ## Relationship To Other Top-Level Directories 51 ## Relationship To Other Top-Level Directories
50 52
51 Services can be thought of as integrators of library code from across the 53 Services can be thought of as integrators of library code from across the
52 Chromium repository, most commonly `//base` and `//mojo` (obviously) but for 54 Chromium repository, most commonly `//base` and `//mojo` (obviously) but for
53 each service also `//components`, `//ui`, *etc.* in accordance with the 55 each service also `//components`, `//ui`, *etc.* in accordance with the
54 functionality they provide. 56 functionality they provide.
55 57
56 Not everything in `//components` is automatically a service in its own right. 58 Not everything in `//components` is automatically a service in its own right.
57 Think of `//components` as sort of like a `//lib`. Individual `//components` can 59 Think of `//components` as sort of like a `//lib`. Individual `//components` can
58 define, implement and use Mojom interfaces, but only `//services` have unique 60 define, implement and use Mojom interfaces, but only `//services` have unique
59 identities with the Service Manager and so only `//services` make it possible 61 identities with the Service Manager and so only `//services` make it possible
60 for Mojom interfaces to be acquired. 62 for Mojom interfaces to be acquired.
61 63
62 ## Adding a new service 64 ## Adding a new service
63 65
64 See the [Service Manager documentation](/services/service_manager) for more 66 See the [Service Manager documentation](/services/service_manager) for more
65 details regarding how to define a service and expose or consume interfaces to 67 details regarding how to define a service and expose or consume interfaces to
66 and from other services. 68 and from other services.
67 69
68 Please start a thread on [services-dev@chromium.org](https://groups.google.com/a /chromium.org/forum/#!forum/services-dev) 70 Please start a thread on [services-dev@chromium.org](https://groups.google.com/a /chromium.org/forum/#!forum/services-dev)
69 if you want to introduce a new service. 71 if you want to introduce a new service.
72
73 If you are servicifying existing Chromium code: Please first read the
74 [servicification strategies documentation](docs/servicification.md), which
75 contains information that will hopefully make your task easier.
OLDNEW
« no previous file with comments | « docs/servicification.md ('k') | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698