[Bug 21735] Map all Wocky errors to an appropriate TpError

[bugzilla-daemon at freedesktop.org]

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

--- Comment #12 from Simon McVittie <simon.mcvittie at collabora.co.uk> 2010-08-11 10:11:02 PDT ---
WOCKY_CONNECTOR_ERROR (first half)
==================================

UNKNOWN currently secretly means internal error in Wocky.

IN_PROGRESS would indicate an internal error in Gabble, if reached.

BAD_JID shouldn't be possible if Gabble has validated the 'account' parameter
correctly; it's not much of a stretch to use InvalidHandle (it's an invalid
thing-that-will-be-a-handle).

NON_XMPP_V1_SERVER isn't relevant to Gabble, which enables legacy Jabber auth,
but it could reasonably be NotImplemented ("your server isn't good enough").

BAD_FEATURES means the server got confused or something. ServiceConfused?

TLS_UNAVAILABLE and TLS_REFUSED should probably both be EncryptionNotAvailable?

TLS_SESSION_FAILED should be EncryptionError.

BIND_UNAVAILABLE is "your server isn't good enough" like NON_XMPP_V1_SERVER.

BIND_FAILED I have no idea; how can it fail?

BIND_INVALID is WOCKY_XMPP_ERROR_BAD_REQUEST in response to binding; see also.

BIND_DENIED is WOCKY_XMPP_ERROR_NOT_ALLOWED in response to binding; see also.

BIND_CONFLICT is handled already.

-- 
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.