We need a FileTransfer LocalFile interface for CM that can't implement the socket one because of the underlying IM library. Such interface would depend on org.freedesktop.Telepathy.Channel.Type.FileTransfer.DRAFT and would have these 2 methods: - ProvideLocalFile(v: path) - AcceptLocalFile(v: path) We should probably define a "LocalFilePath" new TP type as a variant which can be 's' if the path is in UTF-8 and 'ay' if it's not. This interface would also have a "LocalFileOnly" boolean property set to TRUE. Clients would be able to detect if a CM support this interface by looking at RequestableChannelClasses: - if the CM implements just the 'normal' FT mode: {ChannelType: FileTransfer} - if the CM doesn't support Socket FT: {ChannelType: FileTransfer, LocalFileOnly: True} - if the CM implements both it announces the 2 channel classes above.
This just seems wrong... Either we have a single API (and the CM always writes locally (ie that sucks))... or if the CMs library is brain damaged, then the CM should write the file to a temp place.. then, when its over, read it and ship it over the socket... Or override (in LD_PRELOAD style) the read/write functions maybe
From bug #32434: """ Also, if a CM supported a hypothetical Address_Type_Local_File, the handler could just pass that and the file path as the Access_Control_Param to Accept/Provide… ;-) """
-- 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-spec/issues/16.
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.