Re: language/locale selector [was: Re: Settings downstream would reasonably want to add]

[Lennart Poettering <mztabzr 0pointer de>]

On Tue, 17.05.11 12:36, David Zeuthen (zeuthen gmail com) wrote:

> However, when you emit the PropertiesChanged signal on the
> org.fd.DBus.Properties interface, you could pretty please include the
> value for the property that changed as well [0]? The fact you
> currently don't (which Bastien found out after I helped him debug his
> app using your service) means that each instance of each app using
> your interface manually using your service will have to issue a
> Property.Get() method invocation. This is both inconvenient [1] and it
> also causes extra over-head in terms of wakeups etc. from handling
> these extra messages.
> 
> It is true that @invalidated_properties has its place (consider huge
> Blob-like properties), but in this particular case we're talking about
> tens of bytes extra that is emitted every six months or so that
> property changes. So I don't think there's any performance impact.

It's mostly a question of laziness on my side. The
invalidated_properties stuff I can hook up in matter of seconds. The
other props need more work.

I am note against this at all, just lazy ;-)

Lennart

-- 
Lennart Poettering - Red Hat, Inc.