Re: New module proposal: tracker

On Tue, 2009-08-18 at 18:24 +0300, Xan Lopez wrote:
> On Tue, Aug 18, 2009 at 6:21 PM, Lennart Poettering<mztabzr 0pointer de> wrote:
> > On Tue, 18.08.09 11:18, Jamie McCracken (jamie mccrack googlemail com) wrote:
> >
> >>
> >> The indexer part is optional
> >>
> >> The main part tracker-store is just a database with querying and is to
> >> be used by zeitgeist
> >>
> >> If the consensus is that indexer is not suitable for inclusion then the
> >> separate tracker-store should be considered for inclusion separately
> >>
> >> the store does not do any indexing or file monitoring nor does it cosume
> >> significant resources
> >
> > I have no idea what "tracker-store" is. Please elaborate. It sounds as
> > it was the database that is normally filled by the indexing data, but
> > what could it be good for if you rip out the indexer?
> 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? 


Attachment: signature.asc
Description: This is a digitally signed message part

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