[Bug 28797] New: generated client code should be able to set a non-default timeout

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=28797

           Summary: generated client code should be able to set a
                    non-default timeout
           Product: Telepathy
           Version: git master
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: tp-qt4
        AssignedTo: telepathy-bugs at lists.freedesktop.org
        ReportedBy: simon.mcvittie at collabora.co.uk
         QAContact: telepathy-bugs at lists.freedesktop.org


We've been assuming in telepathy-spec design, in at least a few places, that
longer-than-default method timeouts are possible; this makes it possible to
implement RequestContactList() on Conn.I.ContactList and RequestContactInfo on
Conn.I.ContactInfo, for instance.

However, telepathy-qt4 doesn't allow this. On closer inspection, this is really
a QtDBus bug - QDBusAbstractInterface::asyncCall and friends can't set a
non-default timeout either!

It might be possible to work around this with QDBusConnection::callWithCallback
for the few places where we need it.

I think the long-term solution would be for QtDBus to gain this optional
argument:

QDBusPendingCall QDBusAbstractInterface::asyncCallWithArgumentList (const
QString &method, const QList<QVariant> &args, int timeout = -1);

(Requiring construction of a QList<QVariant> for the unusual case is no big
deal, IMO.)

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.