The logger should log file transfers event. A file transfer is mainly a file name, a size, the duration of transfer (which enable ones to compute the mean transfer rate if needed) plus the normal event element, sender/receiver/timestamp etc. Text search for file transfers should match sender/receiver id and alias, along with the file name. Possible issues, one could want to use the file transfer log viewer to find back the file on disk but TP protocol does not give this information, we only know the file basename if my memory is correct.
I agree, the complete pathname would be great to have, also allows clients to let the user open directly for example, etc. I think it might be possible to store the pathname, if the client is nice enough and provides URI http://telepathy.freedesktop.org/spec/Channel_Type_File_Transfer.html#Property:URI Other information useful: * state of the file transfer like cancelled, completed, error, etc. * in general any property that is in the file transfer channel might be useful, for example, the content hash if available, ...
Yeah you should log the URI property, if set, as well.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-logger/issues/18.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.