Re: [Standards] XEP-0313 / XEP-0359 interaction

On 25.03.19 22:07, Dave Cridland wrote: > On Mon, 25 Mar 2019 at 14:03, Florian Schmaus > wrote: > On 25.03.19 13:52, Dave Cridland wrote: > > On Mon, 25 Mar 2019 at 12:26, Florian Schmaus > >

Re: [Standards] XEP-0313 / XEP-0359 interaction

On Mon, 25 Mar 2019 at 14:03, Florian Schmaus wrote: > On 25.03.19 13:52, Dave Cridland wrote: > > > > > > On Mon, 25 Mar 2019 at 12:26, Florian Schmaus > > wrote: > > > > On 25.03.19 12:48, Guus der Kinderen wrote: > > > XEP-0313 "Message Archive Management"

Re: [Standards] XEP-0313 / XEP-0359 interaction

On 25.03.19 13:52, Dave Cridland wrote: > > > On Mon, 25 Mar 2019 at 12:26, Florian Schmaus > wrote: > > On 25.03.19 12:48, Guus der Kinderen wrote: > > XEP-0313 "Message Archive Management" (v0.6.3) relies on XEP-0359 > > "Unique and Stable Stanza IDs" to

Re: [Standards] XEP-0313 / XEP-0359 interaction

We actually use 313/359 to control message delivery from client to local and remote servers. It's a cornerstone of all our protocol extensions. пн, 25 мар. 2019 г. в 17:54, Dave Cridland : > > > On Mon, 25 Mar 2019 at 12:26, Florian Schmaus wrote: > >> On 25.03.19 12:48, Guus der Kinderen

Re: [Standards] XEP-0313 / XEP-0359 interaction

On Mon, 25 Mar 2019 at 12:26, Florian Schmaus wrote: > On 25.03.19 12:48, Guus der Kinderen wrote: > > XEP-0313 "Message Archive Management" (v0.6.3) relies on XEP-0359 > > "Unique and Stable Stanza IDs" to identify content in the archive. > > > > MAM provides an archive on the server, which can

Re: [Standards] XEP-0313 / XEP-0359 interaction

Hi, There is no loss in semantic, the XEP states > The 'by' attribute MUST be set to the address of the archive. so its clear to every client developer at any point in time, what message was archived by the server, and on what message some user or server just added another element. Further

Re: [Standards] XEP-0313 / XEP-0359 interaction

* Guus der Kinderen [2019-03-25 12:48]: > Although this is a simple, elegant solution, it breaks when the client > receives messages that have XEP-0359 IDs, but are not part of the > (server-sided) archive. As far as I can see, it doesn't break as long as the server is aware of the ordering of

Re: [Standards] XEP-0313 / XEP-0359 interaction

On 25.03.19 12:48, Guus der Kinderen wrote: > XEP-0313 "Message Archive Management" (v0.6.3) relies on XEP-0359 > "Unique and Stable Stanza IDs" to identify content in the archive. > > MAM provides an archive on the server, which can be efficiently > synchronized with a client-sided archive. It

Re: [Standards] XEP-0313 / XEP-0359 interaction

On 25 Mar 2019, at 11:48, Guus der Kinderen wrote: > > XEP-0313 "Message Archive Management" (v0.6.3) relies on XEP-0359 "Unique and > Stable Stanza IDs" to identify content in the archive. > > MAM provides an archive on the server, which can be efficiently synchronized > with a client-sided

[Standards] XEP-0313 / XEP-0359 interaction

XEP-0313 "Message Archive Management" (v0.6.3) relies on XEP-0359 "Unique and Stable Stanza IDs" to identify content in the archive. MAM provides an archive on the server, which can be efficiently synchronized with a client-sided archive. It does this using the IDs from XEP-0359. It's a simple

Re: [Standards] Council Voting Summary 2019-03-17

On Sat, 23 Mar 2019 at 09:14, Evgeny wrote: > Hey, Georg, Dave. > > I think I have addressed all your concerns in my new local copy [1] > > [1] http://upload.zinid.ru/xep-eax-cir.html > > Thanks, but for the avoidance of doubt, I had no concerns that needed to be addressed prior to adoption. >