log libpurple/protocols/jabber/adhoccommands.h @ 28655:06fabb28bc69

age author description
Sat, 22 Aug 2009 02:52:30 +0000 Paul Aurich Remove specific copyright lines from the XMPP prpl.
Sat, 22 Aug 2009 02:40:01 +0000 Paul Aurich Update various header copyrights thanks to licensecheck.
Sun, 26 Apr 2009 06:45:55 +0000 Paul Aurich Add a new signal which is emitted (after the account is connected) if the
Sun, 05 Apr 2009 19:21:22 +0000 Paul Aurich Further standardize the sentinel style (did someone say leading _s are theoretically a reserved namespace?)
Fri, 13 Mar 2009 02:26:45 +0000 Paul Aurich Convert all the XMPP IQ callbacks to a typedef similar to the IQ Handlers.
Mon, 25 Jun 2007 20:07:31 +0000 Andreas Monitzer Now all ad-hoc commands have to be sent through jabber_adhoc_execute to be properly executed (including the form steps). This cleans up the code a bit, and avoids DOS attacks by flooding the client with malicious ad-hoc command forms that were not requested.
Mon, 25 Jun 2007 19:08:16 +0000 Andreas Monitzer The server's ad-hoc commands are now listed in the account's action menu. Note that this requires an additional field in the _PurplePluginAction struct. There's no other way, since there was no way to supply user_data, and dynamically created functions are not supported by C. This should be fine, since that struct is only malloced in purple_plugin_action_new, which is part of the core. Applications have to either pass the struct unmodified, or restore the user_data pointer if the action is recreated when necessary (as is the case in Adium).
Sat, 23 Jun 2007 02:57:21 +0000 Andreas Monitzer Implemented ad-hoc commands for the buddy action menu (untested), implemented the receiving end of XEP-0115: Entity Capabilities. Note that this seems not to be reliable right now, since some clients seem to have a very broken [read: completely non-functional] implementation (most notably Gajim and the py-transports).
Tue, 19 Jun 2007 02:53:24 +0000 Andreas Monitzer Implemented XEP-0050: Ad-Hoc Commands. Note that this XEP requires sending an initial command to the peer, which is not implemented in libpurple itself (since this requires a discovery browser or equivalent).