** Changed in: zeitgeist
Status: New => Fix Released
--
Use timestamps with milliseconds granularity (was: use REAL)
https://bugs.launchpad.net/bugs/483603
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant for Zeitgeist Framework.
Sta
I've just fixed recent.py (we don't have information about the
millisecond so we just use seconds*1000), but I'm not sure it's getting
inserted correctly.
** Changed in: zeitgeist
Importance: Undecided => Critical
** Changed in: zeitgeist
Milestone: None => 0.3.0
--
Use timestamps with m
ok so this means i need to change my plugins right? Lets see how
recentlyused manager does it. This might need to be changed!
--
Use timestamps with milliseconds granularity (was: use REAL)
https://bugs.launchpad.net/bugs/483603
You received this bug notification because you are a member of
Zeitg
Yes. Plugins *must* send the timestamps in millis since the Epoch. If
apps only use second granularity then we will have three zeroes in the
end of the timestamps.
--
Use timestamps with milliseconds granularity (was: use REAL)
https://bugs.launchpad.net/bugs/483603
You received this bug notifica
I am a bit confused! Most plugins will send in seconds i think! I doubt they
will send in milliseconds.
Does this mean we will have to convert each entry we get in seconds into
milliseconds?
--
Use timestamps with milliseconds granularity (was: use REAL)
https://bugs.launchpad.net/bugs/483603
Siegfried stated on IRC yesterday that he was in favor of the
milliesecond resolution using an INTEGER column (ie. what we have now).
I think this means that we have rough consensus..?
As for use cases with sub-second resolution think of messaging (IRC,
IM). If I continuously say "spam" on IRC I c
If we really need a millisecond accuracy in timestamps we should go with
INTEGER an use int(time.time()*1000) in python code.
But on the other hand I don't get why we need this at all. Events which happen
at the same time for the user will have a different timestamp, one example is:
A user opens
>> We don't use seconds. We use milliseconds since the Unix epoch.
>Do we?
I believe you meant to say "o rly?!" :-) Anyway, in the places where I've coded
I've used int(time.time()*1000) and time() returns seconds since the Epoch...
While walking the dog I had some further thoughts on why reals/
8 matches
Mail list logo
