Closed
Bug 1311513
Opened 8 years ago
Closed 4 years ago
chrome.storage.sync: develop sharding strategy
Categories
(WebExtensions :: Storage, defect, P3)
WebExtensions
Storage
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: glasserc, Unassigned)
References
Details
(Whiteboard: [storage]triaged)
Make sure we have a plan in place to manage how we will shard data across multiple machines. This plan shouldn't involve any changes to the client, because doing so requires weeks of latency.
|
||
Updated•8 years ago
|
Component: WebExtensions: Untriaged → WebExtensions: General
Priority: -- → P3
Whiteboard: [storage]triaged
|
|
||
Updated•7 years ago
|
Component: WebExtensions: General → WebExtensions: Storage
|
||
Updated•6 years ago
|
Product: Toolkit → WebExtensions
|
||
Comment 1•4 years ago
|
||
This issue sounds like a server-side issue, and it shouldn't be relevant anymore. The new implementation should be using the same server-side infrastructure used for other Firefox syncing features.
Mark,
we may close this issue as wontfix, right?
Flags: needinfo?(markh)
|
||
Comment 2•4 years ago
|
||
Sure can!
Status: NEW → RESOLVED
Closed: 4 years ago
Flags: needinfo?(markh)
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•