| Summary: |
Enhance error reporting for disconnection |
| Product: |
Telepathy
|
Reporter: |
Simon McVittie <smcv> |
| Component: |
tp-spec | Assignee: |
Telepathy bugs list <telepathy-bugs> |
| Status: |
RESOLVED
FIXED
|
QA Contact: |
Telepathy bugs list <telepathy-bugs> |
| Severity: |
normal
|
|
|
| Priority: |
medium
|
|
|
| Version: |
unspecified | |
|
| Hardware: |
Other | |
|
| OS: |
All | |
|
| Whiteboard: |
|
|
i915 platform:
|
|
i915 features:
|
|
|---|
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.
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.