Skip to content

Investigate syncstorage being responsible for TTL settings #641

Open
@pjenvey

Description

@pjenvey

TTL values are currently set per bso by the client.

Our clients only set them on the following collections:

  • history (2 months)
  • forms (3 years)
  • tabs (1 year)
  • clients (3 weeks)

There's no great for the client to manage these settings, does it make more sense for the server to mandate ttls on these collections? Is there any thing the server could do to take advantage of the fact that they're only set on certain collections? That the TTL is really per collection (not bso).

One certain benefit would be the ability to change TTLs without the need for client updates.

Another related fact to consider: Clients only download a certain number of history items by default. Would it make sense to enforce this number of the server (almost like a quota but not).

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions