comparison libpurple/connection.h @ 20114:a465779350aa

Clarified the meaning of PURPLE_REASON_NETWORK_ERROR and PURPLE_REASON_AUTHENTICATION_FAILED, and added PURPLE_REASON_AUTHENTICATION_IMPOSSIBLE. It's not fatal basically because none of the places in prpl-jabber that need it set wants_to_die --- should it be?

20113:1cbda8e2b913

} PurpleConnectionState;

/** Possible errors that can cause a connection to be closed. */
typedef enum
{
	/** There was an error sending or receiving on the network socket. */
	PURPLE_REASON_NETWORK_ERROR = 0,
	/** The username or password was invalid. */
	PURPLE_REASON_AUTHENTICATION_FAILED,
	/** There was an error negotiating SSL on this connection, or encryption
	 *  was unavailable and an account option was set to require it.
	 */
	PURPLE_REASON_ENCRYPTION_ERROR,
	/** Someone is already connected to the server using the name you are

20114:a465779350aa

} PurpleConnectionState;

/** Possible errors that can cause a connection to be closed. */
typedef enum
{
	/** There was an error sending or receiving on the network socket, or
	 *  there was some protocol error (such as the server sending malformed
	 *  data).
	 */
	PURPLE_REASON_NETWORK_ERROR = 0,
	/** The username or password (or some other credential) was incorrect.
	 */
	PURPLE_REASON_AUTHENTICATION_FAILED,
	/** libpurple doesn't speak any of the authentication methods the
	 *  server offered.
	 */
	PURPLE_REASON_AUTHENTICATION_IMPOSSIBLE,
	/** There was an error negotiating SSL on this connection, or encryption
	 *  was unavailable and an account option was set to require it.
	 */
	PURPLE_REASON_ENCRYPTION_ERROR,
	/** Someone is already connected to the server using the name you are