[haiku-development] Re: [haiku-commits] Re: haiku: hrev47664 - src/kits/tracker headers/private/tracker

  • From: Stephan Aßmus <superstippi@xxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Tue, 19 Aug 2014 10:44:14 +0200

Hi,

Am 19.08.2014 01:41, schrieb Axel Dörfler:
On 08/18/2014 09:59 PM, Stephan Aßmus wrote:
On the one hand, I would want the system to inspect files only the
moment I look at them. Including the feature when I scroll down, it
stops scanning files it scheduled while I was looking at the top of the
list and instead scans the ones I look at now. Nautilus does that well
now after annoying me for years.

Why would it want to stop scanning the files scheduled earlier? It
should just scan the files I look at now before. Otherwise I will still
have to wait when I scroll up again after some time.

I'm not sure if Nautilus does that either; maybe it's just the plenty of
cores that give you that idea :-)

Nautilus does, and it's also what I meant, sorry bad wording.

So a tight coupling with Tracker seems like a good idea.

I don't see those as connected. Tracker could just send messages to the
index server which then acts on its work queue as described above.

Yes. I just wanted to point out what kind of control Tracker needs.

I would also move MIME type identification from the registrar to that
server.

Good idea. There are some bugs in that area (concurrent mime sniffing can crash registrar, there is a ticket), and it is not good for such an important component to crash. The functionality that doesn't absolutely have to live there should live elsewhere.

Best regards,
-Stephan



Other related posts: