Re: Using dbus_message_set_data() and dbus_message_get_data() in conjunction with dbus_connection_send_with_reply
Thomas Downing <[email protected]>
| Newsgroups | gmane.comp.freedesktop.dbus |
|---|---|
| Organization | Bomgar |
| Message-ID | <[email protected]> |
As an aside, if I understand what you are doing: round-trippng a pointer in
the presence of such things as async messaging or threads is fraught with
danger.
If I didn't understand, never mind.
td
On Friday, July 24, 2015 11:08:44 Simon McVittie wrote:
> On 24/07/15 14:45, Sahana Vadwa wrote:
> > I'm new to Dbus
>
> Before I answer your actual question, if you are new to D-Bus, perhaps
> you didn't notice these sentences in the front page of the libdbus
> documentation:
>
> This manual documents the low-level D-Bus C API. **If you use this
> low-level API directly, you're signing up for some pain.**
>
> I would strongly recommend using a more friendly D-Bus library, such as
> one of these:
>
> * GDBus (part of Gio, shipped with GLib; C API; independent
> implementation; portable; LGPL)
> * QtDBus (part of Qt; C++ API; wraps libdbus; portable; LGPL)
> * sd-bus (part of systemd; C API; reimplementation; Linux-only; LGPL)
>
> libdbus is the reference implementation. That does not imply that it's
> the *best* implementation, only that it was the *first* implementation,
> and is the one that was used to implement low-level infrastructure like
> dbus-daemon.
>
> > I'm trying to send a particular payload data from my
> > application to dbus via |dbus_message_set_data()|with an intention to
> > get the same data upon calling |dbus_message_get_data()|.
>
> To avoid any misinterpretations: dbus_message_set_data() and
> dbus_message_get_data() are about the message object in memory, not the
> serializable data that can be transmitted across the bus. They are
> mostly intended for language bindings like dbus-python, rather than
> "normal" C API users.
>
> > 1. Create a new dbus method call using |dbus_message_new_method_call()|
> > 2. Allocate a data slot for the DbusMessage
> >
> > using |dbus_message_allocate_data_slot()|
> >
> > 3. Set application payload using |dbus_message_set_data()|
> > 4. Send method call using |dbus_connection_send_with_reply()| ///this
> >
> > is a pending call for which I have a callback registered./
>
> So far, you have one DBusMessage object, which is a method call. However...
>
> > 5. Upon receiving the response for the pending call, get the data set
> >
> > earlier using using |dbus_message_get_data()|
>
> ... the response is a separate DBusMessage object, representing a
> different message. You sent a message of type METHOD_CALL; you got a
> message of type METHOD_REPLY back. They are different serialized
> messages travelling across the bus, and they are also different
> DBusMessage objects in memory. If you attached data to the method call,
> you can only get it back by inspecting the method call, and not by
> inspecting the reply.
>
> If you want to associate in-memory data with a particular
> method-call/reply transaction, the usual way is to pass it to
> dbus_pending_call_set_notify() as the user_data. It will come back into
> your code in the DBusPendingCallNotifyFunction. This should be a
> familiar pattern if you have used asynchronous functions in a library
> like GLib.
>
> Another way to achieve similar results is with
> dbus_pending_call_set_data(), but as with dbus_message_set_data(), you
> don't normally need that unless you are implementing a language binding
> like dbus-python.
<html>
<head>
p.MsoNormal {margin:0in; margin-bottom:.0001pt; font-size:11.0pt; font-
family:"Calibri","sans-serif";}
</head>
<body>
<br>
<div>
<p>
<b><span style="font-size:12.0pt;font-family:"Century
Gothic","sans-serif";color:black">Thomas Downing</span></b><br>
<span style="font-size:9.0pt;font-family:"Century
Gothic","sans-serif";color:#5F6062">Senior Software
Developer<br>+1.601.607.8350<br></span>
</p>
<p>
<span style="font-size:12.0pt;font-family:"Century
Gothic","sans-serif";color:#FF5500">BOMGAR |</span>
<span style="font-size:9.0pt;font-family:"Century
Gothic","sans-serif";color:#FF5500">The Box That's
Revolutionizing Remote Support<sup>™</sup><br></span>
<i><span style="font-size:9.0pt;font-family:"Century
Gothic","sans-serif";color:black">One of the Fastest-
Growing Technology Companies in America | </span></i>
<b><span style="font-size:9.0pt;font-family:"Arial","sans-
serif";color:#00A1DE">Technology Fast 500<sup>™</sup></span></b>
</p>
<p>
<b><span style="font-size:10.0pt;font-family:"Century
Gothic","sans-serif";color:black">What is Bomgar?</span></b>
<span style="font-size:10.0pt;font-family:"Century
Gothic","sans-serif";color:#FF5500"><a
href="http://www.bomgar.com/overview">Find out in 154 seconds.</a></span>
</p>
</div>
</body>
</html>
_______________________________________________
dbus mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/dbus