Resuming Filetransfers doesn't work.

[knuckles@…]

I think this is defined on jep 0096  http://www.jabber.org/jeps/jep-0096.html , which you list as supported in the GajimJepSupport? Trac page.

[nk]

where does it say about resume?

[knuckles@…]

2. Requirements

• Optionally support ranged transfers.

This range should retrieve 256 bytes from the beginning of the file:

Example 5.

<range length='256'/>

This range should retrieve 256 bytes starting from the 128th byte in the file:

Example 6.

<range offset='128' length='256'/>

This range should retrieve the remainder of the file starting at the 128th byte in the file:

Example 7.

<range offset='128'/>

This range is the same as having not sent the range request and the entire file is sent:

Example 8.

<range/>

etc. I see that this is optional, but It's a must-have in any app that does filetransfers.

[knuckles@…]

I've been testing this out with psi and it does use the range as specified in the jep. For example, I started I file transfer, then cancelled it. Then I re-sent the file and here is how psi does the resume request:

<iq type="set" to="xpto/SuSE/Psi" id="aacaa" > <si xmlns=" http://jabber.org/protocol/si" profile=" http://jabber.org/protocol/si/profile/file-transfer" id="s5b_7e3f7530d58a08fb" > <file xmlns=" http://jabber.org/protocol/si/profile/file-transfer" size="3621957632" name="SUSE-10.0-EvalDVD-i386-GM.iso" > <range/> </file> <feature xmlns=" http://jabber.org/protocol/feature-neg"> <x xmlns="jabber:x:data" type="form" > <field type="list-single" var="stream-method" > <option> <value> http://jabber.org/protocol/bytestreams</value> </option> </field> </x> </feature> </si> </iq>

<iq from="xpto/SuSE/Psi" type="result" to="xpto2/SuSE/Psi" id="aacaa" > <si xmlns=" http://jabber.org/protocol/si"> <file xmlns=" http://jabber.org/protocol/si/profile/file-transfer"> <range offset="173146112" /> </file> <feature xmlns=" http://jabber.org/protocol/feature-neg"> <x xmlns="jabber:x:data" type="submit" > <field var="stream-method" > <value> http://jabber.org/protocol/bytestreams</value> </field> </x> </feature> </si> </iq>

The reciever uses range like in the jep to resume the file transfer. I think this should be considered at least for the next version, it's ridiculous not resuming filetransfers in 2006....

[nk]

plz avoid bad language, or pay/donate to Yann who apparently fixed it

thank you