From kde-core-devel  Tue Oct 20 12:04:41 2009
From: Volker Krause <vkrause () kde ! org>
Date: Tue, 20 Oct 2009 12:04:41 +0000
To: kde-core-devel
Subject: Re: Nepomuk as hard dependency in future?
Message-Id: <200910201404.44875.vkrause () kde ! org>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=125604039301342
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart3092580.BLAZTdmYAf"

--nextPart3092580.BLAZTdmYAf
Content-Type: text/plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Tuesday 20 October 2009 13:28:55 Michael Jansen wrote:
> > Making Nepomuk integration optional is quite difficult once you start to
> > depend on it for essential features of your application though. And at
> >  least for KDE PIM, I expect that to happen. In fact, distibution list
> >  resolution already depends on it in some cases.
> >
> > > > but it should be available everywhere our apps travel.
> > >
> > > This is much easier than trying to integrate with native search.
>
> But having to indexing daemon? People already compain about having one of
> them eating up their resources.
>
> Perhaps we could get a two fold strategy. Bring in nepomuk for all the
> semantic features that do not require (strigi?) the indexing demon like
> tagging, rating etc.
>
> And than have a look if we could just hide the indexing part under a laye=
r.
>
> Or am i wrong and nepomuk does not include the indexing part by default?

I'm not sure about the default, but file indexing is independent of the act=
ual=20
Nepomuk functionality and can be disabled separately (systemsettings ->=20
advanced -> desktop search). And the initial file indexing is indeed what=20
gives Nepomuk/Strigi/$SEARCHSERVICE its bad reputation regarding resource=20
consumption. I expect we will see the same for the intial indexing of the=20
data stored in Akonadi.

regards
Volker

--nextPart3092580.BLAZTdmYAf
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iD8DBQBK3adcf5bM1k0S0kcRAkruAKCjWGn6XYd8kF3RaGdhBZw97t50JQCeIGah
zT6T3lqjsPMFF7og2iBJ56o=
=q24t
-----END PGP SIGNATURE-----

--nextPart3092580.BLAZTdmYAf--