Bug 17974 - Enhance error reporting for disconnection
Summary: Enhance error reporting for disconnection
Status: RESOLVED FIXED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: tp-spec (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-08 07:18 UTC by Simon McVittie
Modified: 2009-02-02 03:50 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Simon McVittie 2008-10-08 07:18:20 UTC 
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.
Comment 1 Simon McVittie 2009-02-02 03:50:53 UTC 
Fixed in 0.17.19, although it's now called ConnectionError.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.