add AIM's strange hash algorithm and whatever else is needed for FT
Submitted by Dafydd Harries
Assigned to Telepathy bugs list
Description
Some protocols allow or require a checksum to be sent at the beginning of a file transfer. Currently, we require the client initiating the file transfer to calculate file transfer checksums. Problems with this:
- AIM uses an obscure hash algorishm (and requires the checksum)
Solutions:
-
Declare that requiring clients to implement checksums is not onerous, and maintain the status quo.
-
Implement checksums in the CM. Have the CM be able to read the file twice by:
a) Have clients send the file to the CM before making the offer, and make the CM buffer the file in memory until the offer is accepted or rejected.
b) Have clients send the file to the CM before making the offer, and a second time when the offer is accepted.
c) Allowing clients to pass a filename to the CM, and having the CM read the file.
d) Waiting for file descriptor passing to be included in D-Bus, and allowing clients to pass an open seekable file descriptor to the connection manager before sending the file transfer offer.
My preferred approaches are 0 and 1d.