view libpurple/purple-send @ 24536:c457c635eb8f

Two functional changes here: 1. The default error case for unknown errors on yahoo now uses PURPLE_CONNECTION_ERROR_OTHER_ERROR instead of PURPLE_CONNECTION_ERROR_AUTHENTICATION_FAILED. This change was made because it's logical. 2. The unknown yahoo error with error code "0" now uses PURPLE_CONNECTION_ERROR_NETWORK_ERROR instead of PURPLE_CONNECTION_ERROR_AUTHENTICATION_FAILED. This change was made because this error doesn't seem to be fatal, and we want the account to be reconnected, but normally AUTHENTICATION_FAILED errors are fatal and should not be reconnected Specially this makes yahoo accounts auto-reconnect when we get the error "Unknown error number 0. Logging into the Yahoo! website may fix this." I know we think we fixed this with that change to send the timeout or keepalive much less often, but I'm still seeing a lot of disconnects for it and I have a strong suspicion that they're not actually fatal errors. Refs #5223

#!/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