Chris H-C :chutten Reporter
	Description • 8 years ago

When bug 1218576 is done, it looks as though we'll be sending accumulations batched every 2s or so. This results in our subsessions having "fuzzy edges" where accumulations during one subsession could be applied to a subsequent subsession.

2 seconds' worth of fuzziness isn't the worst thing in the world, but we can do better.

Prevailing idea at time of filing:
* timestamp Accumulations on the child,
* store a timestamp of the last subsession split on the parent,
* use this information to ensure the current subsession hgrams only contain data accumulated during the current subsession.