Log response/error to a method call on the client end
Submitted by Prathmesh Prabhu
Assigned to Simon McVittie
Description
This bug hopes to enrich logging method calls and returns on a dbus-python client.
What: When the dbus client using dbus-python services dbus method calls, it's output/errors are not logged on the client side by default. It would be nice to be able to log this, so that one does not have to go to the other end of the pipe (whoever made the call) to see what the response was. This can be a problem specially because the caller may be dropping errors silently.
How: My current idea is to add two arguments to the dbus.service.method decorator: response_logger, error_logger. When provided, they will log the response, error respsectively that will be returned by the dbus method call, before sending it over the line to dbus server.
What do you think (useful / approach sounds good)?
(The OS field above is linux because that's what I expect to test my patch on)