Opened 9 years ago

Last modified 7 years ago

#5769 new enhancement

Resume broken file transfers

Reported by: Menedas Owned by:
Milestone: Component: libpurple
Version: 2.4.1 Keywords: resume file transfer
Cc:

Description

I would really like to have a resume function for file transfers which gets broken.

Change History (6)

comment:1 Changed 9 years ago by datallah

Whether or not this is even possible is going to depend on whether underlying protocol supports this feature. It looks like there is some support for this concept in XEP-0096, but I don't know about any other protocols.

comment:2 Changed 9 years ago by Menedas

I have tried it with ICQ. With Trillian to Trillian, using ICQ, file transfer resume works. So there are solutions of this in ICQ, too.

But good to know that it could work with XMPP, if it is still implemented in Pidgin.

comment:3 Changed 9 years ago by matthaeus123

I'd love to see this soon.

comment:4 follow-up: Changed 9 years ago by Menedas

I still even can't establish a file transfer over XMPP between two Pidgins yet. It always just about it without an error message. So this should work first.

comment:5 in reply to: ↑ 4 Changed 9 years ago by datallah

  • Component changed from unclassified to libpurple
  • Owner lschiere deleted

Replying to Menedas:

I still even can't establish a file transfer over XMPP between two Pidgins yet. It always just about it without an error message. So this should work first.

This should should work fine with recent versions as long as the sender's server advertises a file transfer proxy, or a working one is manually specified in the sender's XMPP account "Advanced" settings. At any rate, it is unrelated to this ticket, if you've verified the above, you can file a new ticket about the issue and include the debug log.

comment:6 Changed 7 years ago by yeehaw

Is there any word on when this feature might be available?

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!