ArchiveOrangemail archive

dbus.lists.freedesktop.org


(List home) (Recent threads) (85 other Freedesktop.org lists)

Subscription Options

  • RSS or Atom: Read-only subscription using a browser or aggregator. This is the recommended way if you don't need to send messages to the list. You can learn more about feed syndication and clients here.
  • Conventional: All messages are delivered to your mail address, and you can reply. To subscribe, send an email to the list's subscribe address with "subscribe" in the subject line, or visit the list's homepage here.
  • Low traffic list: less than 3 messages per day
  • This list contains about 15,221 messages, beginning May 2003
  • 1 messages added yesterday
Report the Spam
This button sends a spam report to the moderator. Please use it sparingly. For other removal requests, read this.
Are you sure? yes no

DBUS getall method

Ad
Shah, Nirav J2 1333740774Fri, 06 Apr 2012 19:32:54 +0000 (UTC)
Hello,

I have a dbus implementation which is implementing multiple Interfaces inside a single object beside the standard dbus interfaces.  I have 2 questions.

1) The get_all() function takes the interface_name as an input. But this input seems to be optional (at-least according to the qdbusviewer).  According to the specification is it in fact true (for multiple interface usecase).

2) If the input is infact optional and If some of the properties are not always valid. In the situation can the get_all() just skip those properties? I tried this and maybe it's just my implementation but it crashed. Has anyone done something similar? I couldn't find any examples of multiple interface in a single object at all.

PS: By valid I mean it is not always relevant.

Example to clarify the doubt.
//standard Interface each needs to implement
Object 1-> Object1.Dbus.Introspectable
Object 1-> Object1.Dbus.Properties
//implementation specific interfaces.
Object 1 -> Object1.Interface.A
Object 1-> Object1.Interface.B
Object 1 -> Object1.Interface.C

During introspection I am passing a structure with all the properties belonging to all the interfaces.

Each interface has a set of properties which are not always valid for the object. So in the above example for a particular run time scenario properties of Interface.B may not valid.  What is the get all supposed to do then.

Thanks,
Nirav.
Thiago Macieira 1333751753Fri, 06 Apr 2012 22:35:53 +0000 (UTC)
On sexta-feira, 6 de abril de 2012 19.32.31, Shah, Nirav J2 wrote:
> Hello,
> 
> I have a dbus implementation which is implementing multiple Interfaces
> inside a single object beside the standard dbus interfaces.  I have 2
> questions.
> 
> 1) The get_all() function takes the interface_name as an input. But this
> input seems to be optional (at-least according to the qdbusviewer). 
> According to the specification is it in fact true (for multiple interface
> usecase).
> 
> 2) If the input is infact optional and If some of the properties are not
> always valid. In the situation can the get_all() just skip those
> properties? I tried this and maybe it's just my implementation but it
> crashed. Has anyone done something similar? I couldn't find any examples of
> multiple interface in a single object at all.I'd say this situation is not valid. All readable properties are readable allthe time and produce a value. The interpretation of said value is something 
the interface decides, though.

> Example to clarify the doubt.
> //standard Interface each needs to implement
> Object 1-> Object1.Dbus.Introspectable
> Object 1-> Object1.Dbus.Properties
> //implementation specific interfaces.
> Object 1 -> Object1.Interface.A
> Object 1-> Object1.Interface.B
> Object 1 -> Object1.Interface.C
> 
> During introspection I am passing a structure with all the properties
> belonging to all the interfaces.
> 
> Each interface has a set of properties which are not always valid for the
> object. So in the above example for a particular run time scenario
> properties of Interface.B may not valid.  What is the get all supposed to
> do then.Return them anyway, since they *are* valid.
Home | About | Privacy