Re: bring speed back into KConfig

Olivier Goffart <[email protected]> Mon, 21 Apr 2008 22:01:40 +0200
Newsgroups gmane.comp.kde.devel.optimize
Message-ID <[email protected]>
--===============1162529923==
Content-Type: multipart/signed;
  boundary="nextPart1633228.W5G7eWgJmz";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart1633228.W5G7eWgJmz
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Le lundi 21 avril 2008, Dirk Mueller a =E9crit=A0:
> On Friday 18 April 2008, Lubos Lunak wrote:
> >  I've been thinking about making knotify cache few last used configs.
>
> I've a patch based on QCache'ing KNotify::Event's already on my disk,
> waiting for some testing.

I commited recently a patch to cache the KSharedConfigPtr.  (I thought that=
=20
KSharedConfig would have internal cache, but it has not. But maybe it make=
=20
sens to add cache in KSharedConfig instead)

You can't cache KNotify::Event, it may be different for each notification=20
call. Or I misunderstood.

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iD8DBQBIDPKkz58lY8jWrL0RAtTHAJ96SBileAJCLEs8Nvjpuq4nYpikkQCdHoaM
vgsZqo4si5iYznj02jXBWZ4=
=+rp7
-----END PGP SIGNATURE-----

--nextPart1633228.W5G7eWgJmz--

--===============1162529923==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Kde-optimize mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kde-optimize

--===============1162529923==--