Permission to break feature freeze for Nepomuk and Soprano

Matt Rogers mattr at kde.org
Mon Sep 3 16:23:35 BST 2007


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On Sep 3, 2007, at 8:43 AM, Sebastian TrĂ¼g wrote:

> Hi guys,
>
> there has been a long silence around Nepomuk. Well, the main reason  
> is that I
> was working heaviliy on Soprano2 [1]. It comes with a bunch of new  
> features,
> a much cleaner API, a server/client architecture (quite simple but  
> waaaay
> faster than DBus), and I intend to replace the Nepomuk middleware  
> with it. I
> already did it locally and a commit "should" not break anything  
> once Soprano2
> is copied to kdesupport.
>
> The main advantage of all this is: speed. No more DBus for  
> requesting data. It
> is now done via tcp (and I would love some tips and help to add  
> support for
> unix socket communication)
>
> If there are no objections until this evening I will proceed (I  
> know it is
> short notice but I don't think it is such a big deal yet.)
>
> Cheers,
> Sebastian
>
> [1] branches/work/sorano2


What is the impact of this change? If you've done the change locally,  
can you provide a diffstat and the summary of the changes?

You say it has a much cleaner API.
- --
Matt


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (Darwin)

iD8DBQFG3Cb3A6Vv5rghv0cRAgB0AJ9UlKVkObg7iAjHTr9ABH96x6Gq6wCbBaFK
V+jfz2LBUY3bLtLtwQO8mkU=
=0YwN
-----END PGP SIGNATURE-----




More information about the kde-core-devel mailing list