comparison: libpurple/protocols/jabber/jutil.h
libpurple/protocols/jabber/jutil.h
- changeset 29332
- 89bf712a7d11
- parent 29085
- b2ddb2f7bfb9
- child 29336
- 11ae11b31743
equal
deleted
inserted
replaced
| 29331:9e828e599fc2 | 29332:89bf712a7d11 |
|---|---|
| 61 * of the input, or NULL if an error occurred (the string could | 61 * of the input, or NULL if an error occurred (the string could |
| 62 * not be normalized) | 62 * not be normalized) |
| 63 */ | 63 */ |
| 64 char *jabber_saslprep(const char *); | 64 char *jabber_saslprep(const char *); |
| 65 | 65 |
| 66 PurpleConversation *jabber_find_unnormalized_conv(const char *name, PurpleAccount *account); | 66 /** |
| 67 * Search for an IM conversation with this specific user (including resource). | |
| 68 * This is an alternative to purple_find_conversation_with_account(), which | |
| 69 * calls purple_normalize (so if a conversation was found, we'd need to compare | |
| 70 * the conversation name to see if the resources match). | |
| 71 * | |
| 72 * This function saves a call to purple_normalize(), at the expense of | |
| 73 * iterating over every open IM conversation. For most usages, I think | |
| 74 * this tradeoff is OK. | |
| 75 */ | |
| 76 PurpleConversation *jabber_find_unnormalized_im_conv(const char *name, PurpleAccount *account); | |
| 67 | 77 |
| 68 char *jabber_calculate_data_sha1sum(gconstpointer data, size_t len); | 78 char *jabber_calculate_data_sha1sum(gconstpointer data, size_t len); |
| 69 #endif /* PURPLE_JABBER_JUTIL_H_ */ | 79 #endif /* PURPLE_JABBER_JUTIL_H_ */ |
