[Bug 23160] consider not requiring clients to generate checksums for file transfers

[bugzilla-daemon at freedesktop.org]

http://bugs.freedesktop.org/show_bug.cgi?id=23160





--- Comment #3 from Simon McVittie <simon.mcvittie at collabora.co.uk>  2009-08-05 10:52:55 PST ---
Note that FileTransfer has been undrafted (and is part of telepathy-glib's
ABI), so incompatible API changes should be avoided, and we should continue to
support all current FT clients (at least for the file transfers they can
currently do - XMPP and local-XMPP).

As such, FT clients will have to do *some* extra work to support AIM file
transfers, for any of [0], [1a], [1b], [1c], [1d].

Like Daf said, I don't actually think [0] is such a big deal: I don't expect
the list of checksums to get longer than 5-6 (SHA1, SHA256 and MD5 we have,
strange-AIM-checksum we need to add, and maybe CRC32 and/or Adler32 for some
miscellaneous protocol or other). It wouldn't be rocket science to have support
for all of these in each of our current bindings (GLib, Qt4 and Python).


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.