Mercurial > pidgin.yaz
view libpurple/purple-send @ 26795:baa3867f2281
Don't call jabber_parser_close_stream in jabber_close, it papers over a real issue.
As the comment notes and Will pointed out, we should be waiting for the
server to send us a </stream:stream> (or a short-ish timeout) before closing
the connection. That's both non-trivial and probably requires a major bump.
author | Paul Aurich <paul@darkrain42.org> |
---|---|
date | Mon, 27 Apr 2009 16:57:26 +0000 |
parents | 942bf314fc8a |
children | cea56d000b16 |
line wrap: on
line source
#!/bin/sh METHOD_NAME=$1 if test -z "$METHOD_NAME" then cat <<EOF This program calls purple API functions using DBus and prints the return value. If you are not interested in the return value, use purple-send-async. Usage: $0 method-name type1:parameter1 type2:parameter2 ... This shell script just invokes dbus-send, see man dbus-send for how to specify the parameters. Examples: $0 PurpleAccountsFindConnected string: string:prpl-jabber $0 PurpleAccountsGetAll $0 PurpleCoreQuit Use dbus-viewer to get the list of supported functions and their parameters. EOF exit 1 fi shift dbus-send --dest=im.pidgin.purple.PurpleService --print-reply --type=method_call /im/pidgin/purple/PurpleObject im.pidgin.purple.PurpleInterface.$METHOD_NAME "$@" echo