Signal for property changes

[John (J5) Palmieri]

On Mon, 2008-03-24 at 20:28 +0100, Marcel Holtmann wrote:
> Hi J5,
> 
> >>>> did you read the second paragraph of my response? I see that  
> >>>> issue and
> >>>> thus we annotate the properties that do know and in that case we  
> >>>> can
> >>>> send out that signal.
> >>>
> >>> Apparently I did not. Sorry about that.
> >>>
> >>> Indeed, with such an annotation available, it would be possible.
> >>
> >> any ideas about the naming? I am not sure what rules have to be  
> >> followed
> >> for the annotation. Maybe something like:
> >>
> >> 	org.freedesktop.DBus.Property.ChangedSignal
> >
> > You don't need the word Signal in the name.  For instance losing a  
> > name
> > on the bus is org.freedesktop.DBus.NameLost so
> > org.freedesktop.DBus.Property.Changed should be fine.  If someone else
> > used that namespace in their product then it is too bad since that  
> > is a
> > reserved namespace.
> 
> actually this was for the annotation. The signal it self will be  
> Property.Changed, but we have to annotate if this signal will always  
> sent or not. Mainly to make it backward compatible with older  
> specifications and implementations.
> 
> Regards

Hmm, isn't this what interfaces are for? org.freedesktop.DBus.Property2
or org.freedesktop.DBus.ActiveProperty?  Well I guess that would bloat
the spec for a simple change so the annotation seems fine. I would name
it HasChangedSignal or EmitsChangedSignal.

-- 
John (J5) Palmieri <johnp at redhat.com>