Re: [Standards] [XEP-0234] Jingle File Transfer, Last Call and File Sharing

2018-02-28 Thread Ruslan N. Marchenko
Am Dienstag, den 27.02.2018, 15:37 -0700 schrieb Peter Saint-Andre: > On 2/27/18 10:33 AM, Ruslan N. Marchenko wrote: > > That actually touches a point which is nagging me each time I'm > > looking > > into implementation. Who is responsible for closing the session? > > > > According to this [1]

Re: [Standards] [XEP-0234] Jingle File Transfer, Last Call and File Sharing

2018-02-27 Thread Peter Saint-Andre
On 2/27/18 10:33 AM, Ruslan N. Marchenko wrote: > Am Montag, den 26.02.2018, 19:21 -0700 schrieb Peter Saint-Andre: >> >> The idea there was to allow multiple files to be sent in a session; >> you >> wouldn't close the session if you want to send more files, so you >> would >> send the element def

Re: [Standards] [XEP-0234] Jingle File Transfer, Last Call and File Sharing

2018-02-27 Thread Ruslan N. Marchenko
Am Montag, den 26.02.2018, 19:21 -0700 schrieb Peter Saint-Andre: > > The idea there was to allow multiple files to be sent in a session; > you > wouldn't close the session if you want to send more files, so you > would > send the element defined in §8.1 instead. IMHO a good > solution would be t

Re: [Standards] [XEP-0234] Jingle File Transfer, Last Call and File Sharing

2018-02-26 Thread Peter Saint-Andre
On 2/23/18 2:19 AM, Goffi wrote: > Le vendredi 23 février 2018, 10:16:49 CET Goffi a écrit : >> Le vendredi 23 février 2018, 10:02:15 CET Jonas Wielicki a écrit : >>> On Freitag, 23. Februar 2018 09:47:00 CET Goffi wrote: 1) XEP-0234 is in Last Call which is supposed to be finished, what

Re: [Standards] [XEP-0234] Jingle File Transfer, Last Call and File Sharing

2018-02-26 Thread Goffi
Le lundi 26 février 2018, 17:20:15 CET Simon Friedberger a écrit : > Don't you in most cases want hashes anyway to ensure the integrity of > the files? It's calculated during transfer yet, but I don't want to calculate hashed of all the files I'm sharing before sending them. > > It's also not a

Re: [Standards] [XEP-0234] Jingle File Transfer, Last Call and File Sharing

2018-02-26 Thread Simon Friedberger
Don't you in most cases want hashes anyway to ensure the integrity of the files? It's also not actually that resource intensive to calculate the hash of a file. Definitely negligible to transferring it. On 26.02.2018 16:45, Goffi wrote: > > My problem is that I don't want to always calculate has

Re: [Standards] [XEP-0234] Jingle File Transfer, Last Call and File Sharing

2018-02-26 Thread Goffi
Le lundi 26 février 2018, 15:48:49 CET Tobias M a écrit : > 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. My problem is that I don't want to always calculate hashes, it's resource intensive if I have large files

Re: [Standards] [XEP-0234] Jingle File Transfer, Last Call and File Sharing

2018-02-26 Thread Tobias M
> On 26. Feb 2018, at 15:44, Tedd Sterr 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).

Re: [Standards] [XEP-0234] Jingle File Transfer, Last Call and File Sharing

2018-02-26 Thread Tedd Sterr
teful for advertising large numbers of files. Not that it couldn't be extended.. From: Standards on behalf of Goffi Sent: 26 February 2018 13:54 To: XMPP Standards Subject: Re: [Standards] [XEP-0234] Jingle File Transfer, Last Call and File Sharing Hi Tedd, t

Re: [Standards] [XEP-0234] Jingle File Transfer, Last Call and File Sharing

2018-02-26 Thread Goffi
Hi Tedd, thanks for your feedback Le dimanche 25 février 2018, 21:19:16 CET Tedd Sterr a écrit : > The requestor should ask for the full path to the file, not the bare > filename, so as long as you don't have two files with the same name in > the same directory, there shouldn't be a conflict. T

Re: [Standards] [XEP-0234] Jingle File Transfer, Last Call and File Sharing

2018-02-25 Thread Tedd Sterr
> 2) for file sharing, I need more metadata, for instance the path needed to > identify the file gotten from XEP-0329 : I don't want to always calculate > hashes of all files I'm sharing to avoid consuming too much resources, and > the name alone may not identify uniquely the file. > How can I tran

Re: [Standards] [XEP-0234] Jingle File Transfer, Last Call and File Sharing

2018-02-23 Thread Goffi
Le vendredi 23 février 2018, 10:16:49 CET Goffi a écrit : > Le vendredi 23 février 2018, 10:02:15 CET Jonas Wielicki a écrit : > > On Freitag, 23. Februar 2018 09:47:00 CET Goffi wrote: > > > 1) XEP-0234 is in Last Call which is supposed to be finished, what > > > the > > > status about that? > >

Re: [Standards] [XEP-0234] Jingle File Transfer, Last Call and File Sharing

2018-02-23 Thread Goffi
Le vendredi 23 février 2018, 10:02:15 CET Jonas Wielicki a écrit : > On Freitag, 23. Februar 2018 09:47:00 CET Goffi wrote: > > 1) XEP-0234 is in Last Call which is supposed to be finished, what the > > status about that? > > The Council vote isn’t over yet (but from what it looks like, advancemen

Re: [Standards] [XEP-0234] Jingle File Transfer, Last Call and File Sharing

2018-02-23 Thread Jonas Wielicki
On Freitag, 23. Februar 2018 09:47:00 CET Goffi wrote: > 1) XEP-0234 is in Last Call which is supposed to be finished, what the > status about that? The Council vote isn’t over yet (but from what it looks like, advancement will be rejected since Daniels feedback has not been addressed; it looks l

[Standards] [XEP-0234] Jingle File Transfer, Last Call and File Sharing

2018-02-23 Thread Goffi
Hello everybody, As mentioned in my last message, I'm currently working on file sharing. I have a couple of remarks with that: 1) XEP-0234 is in Last Call which is supposed to be finished, what the status about that? 2) for file sharing, I need more metadata, for instance the path needed to i