542315 - Refactor tab sync

Status: RESOLVED WONTFIX

(Firefox :: Sync, enhancement)

Description

[Mike Connor [:mconnor]]

The current implementation writes really big records, one per client.  This puts a non-deterministic cap on the number of tabs that can be successfully synced.  It also means that we are often re-sending data that's already on the server.

Must-have:

* Eliminate the payload-size limitation somehow, by finding an alternate (efficient) alternative to one-record-per-client.

Much-wanted:

* Reduce churn on disk by investigating incremental added records with periodic purge-and-upload-all resets (maybe once per session, or after some percentage of tab churn since first-upload).  Really not picky on impl, but tab writes are a lot of I/O on the server backend, so any improvements here are to be sought.
* Explore group-by-window in a way that UI can capture.
* Ensure that the idea of "moving" or "closing remote" tabs is possible in the future.

Comment 1

[Mike Connor [:mconnor]]

At this point, I don't think any of these pieces are planned or necessary, unless/until there's a move to a new tab group UI which will require more far-reaching work.