Hi chromium-service experts,
I'm working on a feature that allows the Chrome browser to query Updater's policy and display the result in chrome://policy page.
A few relevant information:
- Updater is a standalone process built from //chrome/updater, it's not a long-running one.
- Updater has its own logic to compute its policies. Thus Chrome needs to query the policies by talking to Updater. This is different from most other policies, which Chrome can read/understand directly.
We plan to use mojom as the IPC mechanism between Chrome and Updater. I'd imagine that the IPC server runs inside Updater, and Chrome needs to bootstrap Updater. Does it make sense to servicify this feature? If yes, what's a good candidate location for the service code?
--
Xiaoling