[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: Re: KFileMetaInfo issue
From:       Sebastian =?iso-8859-1?q?Tr=FCg?= <trueg () kde ! org>
Date:       2009-06-18 7:36:41
Message-ID: 200906180936.41891.trueg () kde ! org
[Download RAW message or body]

On Wednesday 17 June 2009 16:16:21 Jos van den Oever wrote:
> 2009/6/10 Sebastian Trüg <trueg@kde.org>:
> > There are two solutions when using Strigi:
> > 1. Hack Strigi to support a fastest flag -> a lot of work I think.
> > Probably not worth it, seeing that there are still analyzers to be
> > ported.
>
> This can be done without hacking strigi but by subclassing
> AnalyzerConfiguration.
> That class determines how much information should be retrieved. You
> can there set the maximal number of bytes allowed to be read.
> If you 'hack' the stream you feed strigi to have a maximal lenght, you
> can receive wrong results, because strigi then thinks the file ends
> prematurely.

aha, nice, did not know that. And what about the analysers? Do they handle 
that or are they forced to only use the configured number of bytes by the 
framework?

Cheers,
Sebastian

[prev in list] [next in list] [prev in thread] [next in thread]