[Bug 49687] New event based LogStore

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed May 9 17:20:50 CEST 2012


--- Comment #5 from Cosimo Alfarano <cosimo.alfarano at collabora.co.uk> 2012-05-09 08:20:50 PDT ---
(In reply to comment #3)
> Good point. How would you propose solving the issue though. I mean with or
> without Zeitgeist if the logger exists we lose the message. Or did I miss
> something?

Seif, the problem is due to fact that the logged info is split in two: Event
Log and Body Index.
Without ZG (the Event Log), there would be just one sync call to Sqlite, to
store the message at once.

We are talking of a clean exit, where for example TPL times out after some time
without channel activities (I don't think it acts that way yet, but it was
supposed to).

The bigger issue is that the second part (body) is the one most likely to be
lost and it's also the most important (or at least equally important with some
other event's info).

I don't care if I don't remember the avatar used with the message or the
geolocation of the event.
I care if I don't have the body or I cannot associate the it with timestamp or

Is there any way to invert the process?

1- write the body with the minimum set of needed info into the Body Index (even
if duplicated in the Log later), assigning a primary key X
2- write the Log, telling ZG that this event is related to X (or giving it our
own event_id).

This is a scenario in which we have a private DB for what we need and delegate
to ZG all the extra data, rather to have the private DB to keep what ZG cannot
store/is better not store in ZG.

Seif, on a (not so) unrelated subject: can you explain how you thought to
manage the "delete event" API? It might be insightful for this problem.
Scenario: TPL's event_id_X is deleted from ZG while TPL is not running?

I don't remember it exactly, but it was a sort of recovery procedure. Can it be
applied in this case? (this would cover the situation for which TPL exists
before ZG returns, not in case ZG does not answer though).

Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA Contact for the bug.
You are the assignee for the bug.

More information about the telepathy-bugs mailing list