Bug 43555 - Feature request: support for variant maps in dbus-send
Summary: Feature request: support for variant maps in dbus-send
Status: RESOLVED MOVED
Alias: None
Product: dbus
Classification: Unclassified
Component: core (show other bugs)
Version: 1.5
Hardware: All All
: low enhancement
Assignee: Havoc Pennington
QA Contact: John (J5) Palmieri
URL:
Whiteboard:
Keywords: patch
Depends on:
Blocks:
 
Reported: 2011-12-06 12:09 UTC by Elly Jones
Modified: 2018-10-12 21:13 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Patch against dbus-1.4.12 to add this feature. (1.71 KB, patch)
2011-12-06 12:09 UTC, Elly Jones
Details | Splinter Review

Description Elly Jones 2011-12-06 12:09:47 UTC
Created attachment 54159 [details] [review]
Patch against dbus-1.4.12 to add this feature.

dbus-send(1) does not support nested containers at all. There is a common idiom of having a{sv} as the last argument of dbus API functions to support later extensions, but dbus-send(1) cannot call these functions. Therefore, add special-case support for a{sv}, which can be done without extending the dbus-send(1) syntax in a backward-incompatible way.

Patch attached.
Comment 1 Simon McVittie 2012-02-08 08:35:16 UTC
Comment on attachment 54159 [details] [review]
Patch against dbus-1.4.12 to add this feature.

Review of attachment 54159 [details] [review]:
-----------------------------------------------------------------

How does this interact with Bug #19807?

Could you please describe how to send an a{sv}, or indeed a{xy} in general, if you've worked out how? I wasn't aware that it was even possible...
Comment 2 GitLab Migration User 2018-10-12 21:13:02 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/dbus/dbus/issues/59.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.