Re: [Standards] Application-level delivery notification between server and client

2013-08-08 Thread Dave Cridland
I know this thread is going to sleep, but I'd like to stick my oar in. :-) On Tue, Aug 6, 2013 at 9:15 PM, Daniele Ricci daniele.ath...@gmail.comwrote: Please correct me if I'm wrong at any point, just to be sure I understand XEP 198 and how I can use it in the right way. XEP-0198 is

Re: [Standards] Application-level delivery notification between server and client

2013-08-08 Thread Daniele Ricci
Hi Dave, thanks for your delightful answer. Actually I was going to reply with pretty much the same arguments, I was looking for the time to write that... you saved me from a long writing :-) Anyway Dave has perfectly catched my needs. Although I ended up defining my own extension, I really would

Re: [Standards] Application-level delivery notification between server and client

2013-08-08 Thread Dave Cridland
On Thu, Aug 8, 2013 at 10:44 AM, Daniele Ricci daniele.ath...@gmail.comwrote: p.s. the last paragraph came 3 times. Ah, sorry. It's very irritating when then happens.

Re: [Standards] Application-level delivery notification between server and client

2013-08-07 Thread Kim Alvefur
On 2013-08-06 22:15, Daniele Ricci wrote: Please correct me if I'm wrong at any point, just to be sure I understand XEP 198 and how I can use it in the right way. First of all, in this: the client or server can send ack elements at any time over the stream this means that I can send a/ or

Re: [Standards] Application-level delivery notification between server and client

2013-08-06 Thread Kevin Smith
On Tue, Aug 6, 2013 at 7:10 PM, Maxim Ignatenko gelraen...@gmail.com wrote: Is there any draft that addresses the problem of silently losing messages when client's TCP connection times out? XEP 198. /K

Re: [Standards] Application-level delivery notification between server and client

2013-08-06 Thread Daniele Ricci
Hi Kevin, XEP 198 lets you acknowlege every stanza in the stream. I want something more specific. Something to confirm messages and return (together with the ack) a message identifier - which is actually a server-side message ID). And all of that in a paranoid way: when a message is sent, server

Re: [Standards] Application-level delivery notification between server and client

2013-08-06 Thread Matthew Wild
On 6 August 2013 20:51, Daniele Ricci daniele.ath...@gmail.com wrote: Hi Kevin, XEP 198 lets you acknowlege every stanza in the stream. I want something more specific. Something to confirm messages and return (together with the ack) a message identifier - which is actually a server-side

Re: [Standards] Application-level delivery notification between server and client

2013-08-06 Thread Daniele Ricci
Please correct me if I'm wrong at any point, just to be sure I understand XEP 198 and how I can use it in the right way. First of all, in this: the client or server can send ack elements at any time over the stream this means that I can send a/ or r/ just for message stanzas. Then it states:

Re: [Standards] Application-level delivery notification between server and client

2013-08-06 Thread Bruce Campbell
On Tue, 6 Aug 2013, Daniele Ricci wrote: Please correct me if I'm wrong at any point, just to be sure I understand XEP 198 and how I can use it in the right way. On Tue, Aug 6, 2013 at 9:58 PM, Matthew Wild mwi...@gmail.com wrote: On 6 August 2013 20:51, Daniele Ricci