So it turns out that the `purple_proxy_connect_socks5_account` does use the Gio proxy code, but then wraps it up in our old file descriptor concepts. Instead, put that code directly in Jabber, which will eventually make it easier to use straight gio instead of file descriptors.
* Add a cancellable on JabberSIXfer.
* Embed SOCKS5 code directly in jabber SI xfer code.
Testing Done:
Compile only.
Reviewed at https://reviews.imfreedom.org/r/201/
/*
* purple
*
* Purple is the legal property of its developers, whose names are too numerous
* to list here. Please refer to the COPYRIGHT file distributed with this
* source distribution.
*
* This program is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Public License as published by
* the Free Software Foundation; either version 2 of the License, or
* (at your option) any later version.
*
* This program is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
* GNU General Public License for more details.
*
* You should have received a copy of the GNU General Public License
* along with this program; if not, write to the Free Software
* Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02111-1301 USA
*
*/
#include"connection.h"
#include"debug.h"
#include"eventloop.h"
#include"idle.h"
#include"log.h"
#include"prefs.h"
#include"savedstatuses.h"
#include"signals.h"
typedefenum
{
PURPLE_IDLE_NOT_AWAY=0,
PURPLE_IDLE_AUTO_AWAY,
PURPLE_IDLE_AWAY_BUT_NOT_AUTO_AWAY
}PurpleAutoAwayState;
staticPurpleIdleUiOps*idle_ui_ops=NULL;
/*
* This is needed for the I'dle Mak'er plugin to work correctly. We
* use it to determine if we're the ones who set our accounts idle
* or if someone else did it (the I'dle Mak'er plugin, for example).
* Basically we just keep track of which accounts were set idle by us,
* and then we'll only set these specific accounts unidle when the