[Adium-devl] Ticket #4501

[Evan Schoenberg]

On Nov 29, 2007, at 11:32 AM, Augie Fackler wrote:

> I'm back from the dead for a moment
Welcome back to the stage of history!

> , and wanted to start a discussion
> on this so that by the time I get time to work on it we actually know
> what I should do. My inclination right now is to create a bundle
> format that would let us resume file transfers in the same way as
> Safari, saving whatever account-specific information is needed for a
> resume.

That sounds quite reasonable to me.  When the transfer's complete, we  
would do a move out of the bundle, which I believe is how Safari  
handles it, too.

> As of now, do any of our account types support resuming a file
> transfer? My guess is no, and therefore we should just implement
> the .adiumFileTransfer bundle for partial downloads which will then be
> more obviously incomplete files (AIM'ing movie files around campus, I
> ended up with some broken ones and was sorely confused for a little
> while).

We do support resuming outgoing AIM transfers when the receiving side  
supports accepting resumed transfers... but I don't think we actually  
resume on receive over AIM.  I don't know of any other protocol which  
potentially supports resumes (though it wouldn't surprise me if some  
XEP somewhere provides specs for doing it over XMPP).

> Does that seem reasonable? Have I missed something? Am I hopelessly
> overengineering?
I can't think of a less-engineered solution which would still work :)

-Evan