Enforce predictor uniqueness through internal registration for AssistRanker |
||
Issue descriptionIn the current state, Ranker does not enforce uniqueness of predictors. This could potentially lead to cache collisions if two predictors point to the same filename. This could be solved by having a predictor registry in AssistRankerService. AssistRankerService would keep ownership of the predictors, and feature clients would request a pointer to a predictor using a unique identifier (which could be the filename).
,
Jan 25 2018
|
||
►
Sign in to add a comment |
||
Comment 1 by bugdroid1@chromium.org
, Dec 15 2017