Who relies on Soprano::Model::statement[s]Added|Removed signals?

[Sebastian Trüg]

of course this is for the frameworks thingi.

On 09/30/2011 07:09 PM, Sune Vuorela wrote:
> On 2011-09-30, Albert Astals Cid <aacid at kde.org> wrote:
>> A Divendres, 30 de setembre de 2011, Sebastian Trüg vàreu escriure:
>>> Hi lists,
>>>
>>> with frameworks in the building and Nepomuk probably going that
>>> direction already for 4.8 I would like to clean up a bit. One of these
>>> cleanup tasks targets the Soprano::Model statement signals. So far these
>>> were the only way to get informed about changes in Nepomuk - with a very
>>> bad impact on performance and bad usability.
>>> With 4.7 we already introduced a preliminary version of the
>>> Nepomuk::ResourceWatcher[1] which is now in charge of informing clients
>>> about changes.
>>> I would like to anyone using the "old" API to change to the new
>>> ResourceWatcher as soon as possible because I would like to disable the
>>> old signals soon. They simply entail to many problems and clutter the API.
>>
>> Removing signals of what seems to be an existing public class/daemon is a very 
>> bad idea and you should wait until 5.0.  
> 
> Full ack.
> 
> /Sune
> 
>