Batching data & timestamp on server about condor

[dominictarr]

oh that is an interesting point.
the purpose of the server timestamp is so that we do not get times that are wildly wrong.
(say, set to the wrong day, or year) we'll still have the relative time from each client
(how long they have been on that page) and we just need the server timestamp so that we can retrive data that happened with a particular range. normally we'd be grabbing ranges that are days or months or at the smallest probably hours, so batching for a few seconds (while not exactly correct) will still be good enough.

[will123195]

I think we do want accurate timestamps.

Here's an idea: The last event in the batch can get normalized to server.now() and all previous events in the batch will be server.now() - n ms.

This way we're always logging with server timestamps and the intervals between events will be preserved.

[dominictarr]

every event will have a localtime, that will be the time elapsed since the page was opened.

hmm. Maybe the solution is to have the client set timestamps, and just to validate them on the server?

If the timestamp is within a givin range, then let it be, but if it's outside of that range then set a new timestamp to the current server time.

[kesla]

Here's how this works now:

We have 3 fields:

• duration - that's how many ms a user has been on the page since the script was initiaded
• timestamp - timestamp in UTC when the event happens
• timezone - the timezone the user is in

These combined should make it possible for us to do batch requests. Please reopen this issue if there's something that I've forgotten about.