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

[bugzilla-daemon at freedesktop.org]

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

           Summary: consider not requiring clients to generate checksums for
                    file transfers
           Product: Telepathy
           Version: unspecified
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: telepathy-spec
        AssignedTo: telepathy-bugs at lists.freedesktop.org
        ReportedBy: dafydd.harries at collabora.co.uk
                CC: tester at tester.ca, simon.mcvittie at collabora.co.uk,
                    will.thompson at collabora.co.uk,
                    jonny.lamb at collabora.co.uk


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:

 1. AIM uses an obscure hash algorishm (and requires the checksum)

Solutions:

 0. Declare that requiring clients to implement checksums is not onerous, and
maintain the status quo.

 1. 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.


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