log libpurple/protocols/jabber/adhoccommands.c @ 25147:8bc9f89f305e

age author description
Sat, 10 Nov 2007 12:10:04 +0000 Will Thompson propagate from branch 'im.pidgin.pidgin' (head d8103be97302efb404e2f6922925f661c807ad23)
Fri, 09 Nov 2007 02:00:15 +0000 Andreas Monitzer Fixed cancelling ad-hoc commands
Tue, 09 Oct 2007 13:32:58 +0000 Will Thompson Stop jabber setting wants_to_die itself. This involved plumbing disconnection
Sat, 15 Sep 2007 18:27:01 +0000 Sadrul Habib Chowdhury Plug some memory leaks.
Fri, 14 Sep 2007 00:17:33 +0000 Daniel Atallah There shouldn't be assert()s in pretty much any libpurple code.
Mon, 10 Sep 2007 14:46:13 +0000 Daniel Atallah Various warning fixes for the xmpp prpl.
Mon, 10 Sep 2007 14:37:40 +0000 Daniel Atallah Fix mingw build of xmpp prpl
Tue, 17 Jul 2007 01:15:18 +0000 Andreas Monitzer Implemented error handling for ad-hoc commands.
Mon, 16 Jul 2007 03:44:09 +0000 Andreas Monitzer Switched formatting of the ad-hoc commands to be less intimidating
Fri, 13 Jul 2007 15:34:16 +0000 Andreas Monitzer Now showing ad-hoc commands of other clients connected to the same account in the account menu (per XEP-0146). Since it is becoming messy in that menu, I also prefixed all ad-hoc commands with the node this command belongs to in [], which is the resource name for clients and the domain name for the server. Examples: "[home] Set status" for clients and "[jabber.org] Send message to all connected users" for servers.
Wed, 11 Jul 2007 02:36:42 +0000 Andreas Monitzer Fixed a bug that prevented multi-stage ad-hoc commands.
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 14:50:22 +0000 Andreas Monitzer Added the ability to register gateways, re-using most of the account registration code for this.
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).