Re: [Tracker] When to index files
- From: Ivan Frade <ivan frade gmail com>
- To: Aleksander Morgado <aleksander lanedo com>
- Cc: "Tracker \(devel\)" <tracker-list gnome org>
- Subject: Re: [Tracker] When to index files
- Date: Thu, 25 Nov 2010 18:59:20 +0200
Hi,
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.
Regards,
Ivan
On Thu, Nov 25, 2010 at 6:47 PM, Aleksander Morgado
<aleksander lanedo com> wrote:
Hoola,
Currently updated files are indexed by tracker if GIO issues a
G_FILE_MONITOR_EVENT_CHANGES_DONE_HINT event. This event may happen due
to two different reasons:
a) The process which updated the file close()d it.
b) The process which updated the file didn't close it, but 2 seconds
elapsed since the last write() done to the file.
This 2 second delay is currently hardcoded, but I already implemented a
patch for GLib to set it configurable or even to disable the whole b)
case:
https://bugzilla.gnome.org/show_bug.cgi?id=635765
The question now is, which should be the default tracker behavior?
* Only index the file if the process which updated it close()d it?
(a-only case)
* Or also index the file even if the process didn't close() it but some
time happened since the last write()? (a+b case, as we currently do)
Does anyone have strong feelings for one or the other approach?
Cheers,
--
Aleksander
_______________________________________________
tracker-list mailing list
tracker-list gnome org
http://mail.gnome.org/mailman/listinfo/tracker-list
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]