| commit | 068193b4c6f6667c1d08febfd30089a1ea0283e8 | [log] [tgz] |
|---|---|---|
| author | Vardhan Mudunuru <vardhan@google.com> | Fri Nov 09 15:27:19 2018 -0800 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Thu Nov 15 22:48:09 2018 +0000 |
| tree | 3f34831ff8a3f787ee29f17ac685a9c1c6b5f77a | |
| parent | 05d6ebca64b7bb55aca3ef45dbcbc05e7ee3c36f [diff] |
[modular] Teach the framework to read module facets
By using ModuleFacetReader.
* ModuleFacetReader is plumbed to AddModCall
* AddModCall will use ModuleFacetReader to read the data out of the
package in the event that the resolver doesn't know about the module
manifest; otherwise, we can use what the resolver knows about. This
gating needs to be refined more since there may be problematic cases:
* What if the resolver's version of the package is out-of-date
compared to the actual package contents, since we don't have any
sense of versioning? e.g., if the package was updated without the
resolver knowing about it.
* Convert common_null_module and common_active_module to supply module
facets in their .cmx files.
Test=AddModCommandRunnerTest.ReadModFacetIfNoResolverResponse and all
integration tests that use common_active_module and common_null_module
Change-Id: I81b5e1305a0549372016f8606a95b0f31c80555e
Peridot is a framework for composed, intelligent and distributed user experiences.
Applications not explicitly designed to interoperate (and possibly implemented in different programming languages) are ephemerally downloaded and dynamically composed to run in a shared context. The framework manages application lifecycle, resources and view hierarchy; and well as context and suggestion infrastructure.
State of Peridot experiences is transparently synchronized across user devices using a distributed offline-first storage system.