Mercurial > pidgin.yaz
comparison libpurple/connection.h @ 20110:ed4c1053c3da
Add PURPLE_REASON_INVALID_USERNAME, which should go away as soon as there's
some hook for prpls to validate the account settings before connecting.
author | Will Thompson <will.thompson@collabora.co.uk> |
---|---|
date | Tue, 18 Sep 2007 21:12:28 +0000 |
parents | d3bd5414eb0f |
children | a465779350aa |
comparison
equal
deleted
inserted
replaced
20109:94062344397c | 20110:ed4c1053c3da |
---|---|
68 PURPLE_REASON_ENCRYPTION_ERROR, | 68 PURPLE_REASON_ENCRYPTION_ERROR, |
69 /** Someone is already connected to the server using the name you are | 69 /** Someone is already connected to the server using the name you are |
70 * trying to connect with. | 70 * trying to connect with. |
71 */ | 71 */ |
72 PURPLE_REASON_NAME_IN_USE, | 72 PURPLE_REASON_NAME_IN_USE, |
73 | |
74 /** The username for the account isn't valid. | |
75 * @todo This reason really shouldn't be necessary. Usernames and | |
76 * other account preferences should be validated when the | |
77 * account is created. | |
78 */ | |
79 PURPLE_REASON_INVALID_USERNAME, | |
73 | 80 |
74 /** The server did not provide a SSL certificate. */ | 81 /** The server did not provide a SSL certificate. */ |
75 PURPLE_REASON_CERT_NOT_PROVIDED, | 82 PURPLE_REASON_CERT_NOT_PROVIDED, |
76 /** The server's SSL certificate could not be trusted. */ | 83 /** The server's SSL certificate could not be trusted. */ |
77 PURPLE_REASON_CERT_UNTRUSTED, | 84 PURPLE_REASON_CERT_UNTRUSTED, |