Mechanism to expose information to clients outside Chrome. |
|||
Issue descriptionThere are an increasing number of times when Chrome needs to expose information to clients which are run independently of Chrome. Sometimes, these clients may run even before Chrome has started. In the past, we've used arbitrary .dotfiles on the stateful partition to expose this information. We should standardize on the mechanism we want to use to expose this information - with a design clarifying the reasons for picking the mechanism over any other alternatives.
,
Apr 13 2017
A short design doc for this feature is here: http://go/chrome-properties-cros
,
Apr 24 2017
This is superseded by work being done by mnissler@ - see comments on the design doc.
,
Apr 30 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by r...@chromium.org
, Mar 29 2017