Re: [Tracker] When to index files




  I'd say only when closed. I wonder in what case could be useful to
index a file that is still in use. It will be incomplete and useless for
the user.

The case for the N900 was: You download a large file and you want 
progress updates to know about it in some UI. Of course, the close() 
doesn't come for a long time for large files and in that case, you may 
want to know about the existence of the file before it was fully downloaded.

We have since considered this situation a corner case and uncommon, for 
applications that really care about that, they can use inotify 
themselves instead of depend on Tracker. There isn't anything 
interesting about the file before it is close()d in Tracker anyway as 
you say Ivan (i.e. size, type, extracted metadata is either unset or 
always changing).

Additionally, the extra house keeping required for a cache and dealing 
with changing files just adds extra maintenance for a limited set of use 
cases.

So I think we all agree, only close() really make sense.


Great then, let's do it only on close(). We'll need to wait for the GIO
patch to get reviewed and released, and then possibly tweak the
tracker-monitor internals a little bit, but that's always fun.

Cheers,

-- 
Aleksander




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