HGKeeper

Embed SOCKS5 proxying in Jabber SI xfer code

2020-11-05, Elliott Sales de Andrade

f2d29265494b

Embed SOCKS5 proxying in Jabber SI xfer code

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/

<?xml version='1.0' encoding="ISO-8859-1"?>

<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"

"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" [

<title>Log signals</title>

<title role="signal_proto.title">List of signals</title>

"<link linkend="logs-log-timestamp">log-timestamp</link>"

</synopsis>

</refsect1>

<title role="signals.title">Signal details</title>

<title>The <literal>"log-timestamp"</literal> signal</title>

char * user_function (PurpleLog *log,

time_t when,

gboolean show_date,

gpointer user_data)

</programlisting>

<para>

Emitted to allow plugins to customize the timestamp on a message being logged.

</para>

Plugins must be careful of logs with a type of PURPLE_LOG_SYSTEM.

</para></note>

<listitem><simpara>The log the message belongs to.</simpara></listitem>

</varlistentry>

<listitem><simpara>The time to be converted to a string.</simpara></listitem>

</varlistentry>

<listitem><simpara>Whether the date should be displayed.</simpara></listitem>

</varlistentry>

<listitem><simpara>user data set when the signal handler was connected.</simpara></listitem>

</varlistentry>

<term><emphasis>Returns</emphasis> :</term>

<listitem><simpara>A textual representation of the time, or <literal>NULL</literal> to use a default format.</simpara></listitem>

</varlistentry>

</variablelist>

</refsect2>

</refsect1>

</chapter>

pidgin/pidgin