<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On 27 Jan 2015, at 07:11, Vladan Djeric <<a href="mailto:vdjeric@mozilla.com">vdjeric@mozilla.com</a>> wrote:</div><blockquote type="cite"><div dir="ltr"><span><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex; position: static; z-index: auto;"><div style="word-wrap:break-word"><span><blockquote type="cite"><div dir="ltr"><ul><li>In the new system, Firefox starts collecting a new ping whenever:</li><ol><li>a new Firefox session is started</li><li>a new day has begun (not sure if it's every 24 hours of uptime, or if it's based on local time e.g. midnight local time)</li></ol></ul></div></blockquote></span>That was a partially open question, midnight local time is what we will do unless there is useful counter arguments.</div></blockquote><div><br></div></span><div>If
FHR analyses are based around local time, we have to start pings on
midnight local time. This raises some challenges for how we store the
submitted pings server-side. The S3 archives are currently organized by
submission date not (local) <u>collection</u> date. This discussion is probably better to have in person with Mark.<br></div></div></blockquote><div><br></div>If the splitting of the session at that point is a problem, let me know - i don’t know what the server-side requirements for organisation are.</div><div>We do need to split at some point for the 24h submission interval, midnight local time was brought up as a probably convenient cut-time.</div><div>What exact time we choose shouldn’t matter too much?</div><div><br></div><div>Georg</div></body></html>