> On 26. Feb 2018, at 15:44, Tedd Sterr <[email protected]> wrote:
>
> I see your point now - I was looking at XEP-0329 (File Information Sharing),
> where the shared files are requested using a full path; while your issue is
> that XEP-0234 (Jingle File Transfer) only wants a single file name (without
> path).
>
> So, presumably, the files are advertised via 0329 (with paths), then when a
> requester decides which file they want, they ask (with path) for its info -
> the info includes filename (no path) & hash, which can then be used to
> initiate the 0234 transfer (?)
>
> If you have two files with the same filename and hash, but in different
> paths, does it actualy matter which one you send (they're essentially
> identical) ...or the date stamp chould be included as well (at which point,
> maybe a UUID is less work.)
>
> XEP-0358 (Publishing Available Jingle Sessions) could provide a more
> appropriate mechanism (with IDs!), though it might be wasteful for
> advertising large numbers of files. Not that it couldn't be extended..
If XEP-0329 would also share the hashes, you could use the hash to to fetch
things via Jingle FT, similar to what XEP-0385 does.
Cheers,
Tobi
_______________________________________________
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: [email protected]
_______________________________________________
