aboutsummaryrefslogtreecommitdiffstats
path: root/doc/user-guide
diff options
context:
space:
mode:
authorulim <a.sporto+bee@gmail.com>2007-12-04 01:53:04 +0100
committerulim <a.sporto+bee@gmail.com>2007-12-04 01:53:04 +0100
commitfa30fa598d2e77c998f9156d0f31ccf99b0c781f (patch)
treef238de491573827510c55e29cf80e2fda7ccc793 /doc/user-guide
parent2c2df7dd91930345a9b22a8bb61327d1dcc7e3d5 (diff)
parentdce390357114e30a424106c99e49cef1e682e1af (diff)
Jabber file transfer now also with sending! You can't use a proxy yet when
sending, that's my next task. You can use proxies when receiving though! I also changed the buffering strategy. Previously receiving continued till some buffer limit was reached, now only one message is received and receiving stops till it is delivered. This keeps the buffering space per file transfer to a minimum(currently 4k). Makes sense when used on a public server. For public servers a throughput maximum would also be interesting...
Diffstat (limited to 'doc/user-guide')
-rw-r--r--doc/user-guide/commands.xml43
1 files changed, 43 insertions, 0 deletions
diff --git a/doc/user-guide/commands.xml b/doc/user-guide/commands.xml
index ac9bdf11..8c874014 100644
--- a/doc/user-guide/commands.xml
+++ b/doc/user-guide/commands.xml
@@ -860,4 +860,47 @@
</ircexample>
</bitlbee-command>
+
+ <bitlbee-command name="transfers">
+ <short-description>Monitor, cancel, or reject file transfers</short-description>
+ <syntax>transfers [&lt;cancel&gt; id | &lt;reject&gt;]</syntax>
+
+ <description>
+ <para>
+ Without parameters the currently pending file transfers and their status will be listed. Available actions are <emphasis>cancel</emphasis> and <emphasis>reject</emphasis>. See <emphasis>help transfers &lt;action&gt;</emphasis> for more information.
+ </para>
+
+ <ircexample>
+ <ircline nick="ulim">transfers</ircline>
+ </ircexample>
+ </description>
+
+ <bitlbee-command name="cancel">
+ <short-description>Cancels the file transfer with the given id</short-description>
+ <syntax>transfers &lt;cancel&gt; id</syntax>
+
+ <description>
+ <para>Cancels the file transfer with the given id</para>
+ </description>
+
+ <ircexample>
+ <ircline nick="ulim">transfers cancel 1</ircline>
+ <ircline nick="root">Canceling file transfer for test</ircline>
+ </ircexample>
+ </bitlbee-command>
+
+ <bitlbee-command name="reject">
+ <short-description>Rejects all incoming transfers</short-description>
+ <syntax>transfers &lt;reject&gt;</syntax>
+
+ <description>
+ <para>Rejects all incoming (not already transferring) file transfers. Since you probably have only one incoming transfer at a time, no id is neccessary. Or is it?</para>
+ </description>
+
+ <ircexample>
+ <ircline nick="ulim">transfers reject</ircline>
+ </ircexample>
+ </bitlbee-command>
+ </bitlbee-command>
+
</chapter>