diff options
author | Stef Walter <stefw@redhat.com> | 2014-02-21 16:59:48 +0100 |
---|---|---|
committer | Jakub Hrozek <jhrozek@redhat.com> | 2014-03-14 13:42:31 +0100 |
commit | 06b7bc8ca2e005ed510210d3b8dee16afbabbcc9 (patch) | |
tree | 8131673e499cced272643b379d1a754c064f76b2 /src/resolv | |
parent | f5e47e1d65f80ffdb1893feab18583a74d661214 (diff) | |
download | sssd-06b7bc8ca2e005ed510210d3b8dee16afbabbcc9.tar.gz sssd-06b7bc8ca2e005ed510210d3b8dee16afbabbcc9.tar.xz sssd-06b7bc8ca2e005ed510210d3b8dee16afbabbcc9.zip |
sbus: Add the sbus_request_parse_or_finish() method
Some DBus types returned from dbus_message_get_args() require memory
to be released when done. We automatically attach these to the talloc
struct sbus_request memory context in this function.
This accepts varargs similar to dbus_message_get_args(), which are
rather awkward. However instead of reworking them completely, future
generated marshalling code will replace most uses of these varargs.
If parsing the dbus message fails, then it responds to the DBus caller
with an appropriate error such as o.f.D.Error.InvalidArgs. In these
cases (ie: when it returns FALSE) the sbus_request is finished.
Migrated some, but not all, uses of dbus_message_get_args() to the
new function. Some instances have uncommon semantics such as terminating
the connection upon failure to parse a message.
Reviewed-by: Jakub Hrozek <jhrozek@redhat.com>
Reviewed-by: Pavel Březina <pbrezina@redhat.com>
Reviewed-by: Lukáš Slebodník <lslebodn@redhat.com>
Diffstat (limited to 'src/resolv')
0 files changed, 0 insertions, 0 deletions