dbus_message_demarshal() and partial messages
Havoc Pennington
hp at redhat.com
Fri Aug 17 14:55:46 PDT 2007
Hi,
On 8/17/07, Avery Pennarun <apenwarr at gmail.com> wrote:
> Having now done it (I'm linking with libdbus statically so I can
> access its internal functions for now), I can confirm that only the
> one new function is needed, and its implementation is pretty much
> trivial as discussed.
Propose the exact API (was that in the previous message? I forget ;-)
> There's also a question of how a serial number gets set: unless I'm
> mistaken, dbus_marshal() doesn't set it. You have to lock the message
> first, but that's private too. dbus_marshal() should do that,
> perhaps?
The next serial to use is a property of the outgoing queue, so in this
case libdbus won't know what it is. dbus_message_set_serial() could be
made public I suppose.
Havoc
More information about the dbus
mailing list