Mercurial > pidgin
view libpurple/dbus-define-api.h @ 28315:d9eb51a3a3a2
jabber: Don't try to pull a photo out of the <PHOTO/> cdata.
When the data from the server looks literally like:
<PHOTO>
<TYPE>image/jpeg</TYPE>
<BINVAL></BINVAL>
</PHOTO>
xmlnode_get_data(photo_node) will contain (whitespace) data, but in
no way is it a base64-encoded image. I can't find any reference to
clients distributing avatars in that way in the XEP or the RFC.
author | Paul Aurich <paul@darkrain42.org> |
---|---|
date | Sat, 03 Oct 2009 02:50:48 +0000 |
parents | 32c366eeeb99 |
children |
line wrap: on
line source
#error "This is file is not a valid C code" /* This file contains some of the macros from other header files as function declarations. This does not make sense in C, but it provides type information for the dbus-analyze-functions.py program, which makes these macros callable by DBUS. */ /* blist.h */ gboolean PURPLE_BLIST_NODE_IS_CHAT(PurpleBlistNode *node); gboolean PURPLE_BLIST_NODE_IS_BUDDY(PurpleBlistNode *node); gboolean PURPLE_BLIST_NODE_IS_CONTACT(PurpleBlistNode *node); gboolean PURPLE_BLIST_NODE_IS_GROUP(PurpleBlistNode *node); gboolean PURPLE_BUDDY_IS_ONLINE(PurpleBuddy *buddy); gboolean PURPLE_BLIST_NODE_HAS_FLAG(PurpleBlistNode *node, int flags); gboolean PURPLE_BLIST_NODE_SHOULD_SAVE(PurpleBlistNode *node); /* connection.h */ gboolean PURPLE_CONNECTION_IS_CONNECTED(PurpleConnection *connection); gboolean PURPLE_CONNECTION_IS_VALID(PurpleConnection *connection); /* conversation.h */ PurpleConvIm *PURPLE_CONV_IM(const PurpleConversation *conversation); PurpleConvIm *PURPLE_CONV_CHAT(const PurpleConversation *conversation);