[USS] Allow services to specify a storage key |
||
Issue descriptionRight now the ModelTypeService implementations must use client tag to communicate with the processor. This is bad for a couple reasons 1) Client tag has to be backwards compatible with pre-USS clients. 2) Client tag might be very large, for typed urls this could be many KB each. 3) Client tag is often not easily useful for the service. They may want a composite key that consists of multiple different values, and parsing apart a string with constant prefix is a hassle.
,
Aug 16 2016
At this point we are going to leave it as a std::string. Services that want complex/multipart keys can serialize a proto into the storage key. |
||
►
Sign in to add a comment |
||
Comment 1 by bugdroid1@chromium.org
, Aug 11 2016