Re: New module proposal: tracker

On Tue, Aug 18, 2009 at 6:36 PM, Maciej Piechotka<uzytkownik2 gmail com> wrote:
>> It can be used directly by applications that feed it data through an
>> API. Zeitgeist is an example, another could be bookmarks/history
>> storage in Epiphany.
>> Xan
> Hmm. Is it one-in-all database? Then:
> - How you keep it out of corruption. Hardware and software errors
> happens and sometimes one lost files. If it is one file - ok I can live
> with it. If it is one-in-all file - ops (and please note that average
> user does not make backup).
> - Some fs makes operations with small files much more efficient then
> bigger (reiser* for example). It may have performance impact.
> - What with concurrent access?

I have no idea if Tracker uses just one huge file for everything or if
it can use one file per application/domain/whatever (and in any case
that's an implementation detail not terribly important for this debate
IMHO). My only point is that something like tracker-store is already
useful even if you don't ship a single filesystem miner with it. You
could even argue that in many cases it's better for the apps to feed
the data directly to tracker and cut the middleman of writing it into
the filesystem for miners to find it at a later point.


> Regards

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]