Reply limits exceeded problems
oliv__a at users.sourceforge.net
Mon Aug 9 14:53:56 PDT 2004
Havoc Pennington [Sun, 08 Aug 2004]:
> On Sun, 2004-08-08 at 16:43, Olivier Andrieu wrote:
> > Maybe we could add a convenience function so that message
> > handlers (server implementations) can easily send a reply without
> > data. Something like this:
> I think what we have here is another symptom of the D-BUS API designed
> to be the low-level backend for the GLib/Python/Qt bindings.
> Using any of those bindings, the reply should be sent
Sure. But the plain C binding is still necessary I think: David is
using plain C for libhal. I don't think he plans to use GLib (maybe he
does I don't know) ?
> > Also, maybe dbus_connection_send() could automatically call
> > dbus_message_set_no_reply() on the message ? In other words, make
> > the status of the no_reply flag consistent with the way the
> > message is sent, i.e. with _connection_send() or
> > _connection_send_with_reply() ?
> Right now connection_send() returns the client serial, which is
> only useful if you're going to use it to identify the reply
> later... what with_reply() adds is that it automatically deals with
> finding the reply, timing it out, and so forth.
Ah yes, I forgot about the reply serial.
> Which is to say, maybe we should do this but if we did we'd have to
> drop the client_serial return.
which is needed in the daemon implementation daemon I guess.
More information about the dbus