[Telepathy] [Bug 17974] New: Enhance error reporting for disconnection

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Oct 8 07:18:20 PDT 2008


           Summary: Enhance error reporting for disconnection
           Product: Telepathy
           Version: unspecified
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: telepathy-spec
        AssignedTo: telepathy at lists.freedesktop.org
        ReportedBy: simon.mcvittie at collabora.co.uk

StatusChanged currently indicates the reason for disconnection using an enum,
for which the Telepathy project is the naming authority. This doesn't really
scale if CMs want to report protocol-specific disconnection reasons.

We should add a signal, something like: DisconnectionReason(s
(DBus_Error_Name): Error)

Newer CMs would emit
DisconnectionReason('com.example.ProtocolSpecific.FellDownAWell') immediately
followed by StatusChanged(DISCONNECTED, REASON_ERROR), allowing a more specific
error to be given.

Newer client code would consider the connection to be dead when either
DisconnectionReason or StatusChanged(DISCONNECTED, .) happened, whichever was
first; this would work with either old or new CMs.

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

More information about the Telepathy mailing list