Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhancement: Support viewer needs two kinds of compression #37

Open
awkay opened this issue Oct 4, 2016 · 0 comments
Open

Enhancement: Support viewer needs two kinds of compression #37

awkay opened this issue Oct 4, 2016 · 0 comments

Comments

@awkay
Copy link
Contributor

awkay commented Oct 4, 2016

Transmitting a support request is currently very expensive. We could compress history into a single snapshot followed by a sequence of diffs (one per tx).

The second kind of compression needed is being able to mark a transaction as "skippable", primarily for form-text input (e.g. every keystroke makes a new history entry). The rules would be: two or fewer adjacent "skippable" entries are left alone. Three or more cause all the "middle ones" to not be recorded at all such that you always end up with one or two "skippable" entries in history for any sequence. The first (and only) is the "one" case. The first and last are the "many" case.

Implementation-wise, this is essentially "overwrite the last history entry if that entry is skippable and the prior entry is ALSO skippable".

Might be nice to get this latter bit into Om as a PR somehow.

@awkay awkay changed the title Support viewer needs two kinds of compression Enhancement: Support viewer needs two kinds of compression Oct 13, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant