Re: [Standards] Exact hint for Result Set Management

2018-07-12 Thread Dave Cridland
On 12 July 2018 at 12:24, Florian Schmaus wrote: > On 12.07.2018 12:39, Kevin Smith wrote: > > On 12 Jul 2018, at 11:23, Matthew Wild wrote: > >> > >> On 11 July 2018 at 18:25, Florian Schmaus wrote: > >>> On 11.07.2018 18:01, Matthew Wild wrote: > On 11 July 2018 at 16:33, Florian

[Standards] Exact hint for Result Set Management

2018-07-12 Thread Florian Schmaus
On 12.07.2018 15:20, Matthew Wild wrote: > On 12 July 2018 at 13:13, Florian Schmaus wrote: >> I'm well aware why RSM allows inexact results. That is not what this PR >> is about. >> >> I simply think it is an oversight that RSM does not signal if the >> results are exact or not. > > Then I

Re: [Standards] Exact hint for Result Set Management

2018-07-12 Thread Matthew Wild
On 12 July 2018 at 13:13, Florian Schmaus wrote: > I'm well aware why RSM allows inexact results. That is not what this PR > is about. > > I simply think it is an oversight that RSM does not signal if the > results are exact or not. Then I think you didn't quite consider my points? The count

Re: [Standards] Exact hint for Result Set Management

2018-07-12 Thread Florian Schmaus
On 12.07.2018 12:23, Matthew Wild wrote: > On 11 July 2018 at 18:25, Florian Schmaus wrote: >> On 11.07.2018 18:01, Matthew Wild wrote: >>> On 11 July 2018 at 16:33, Florian Schmaus wrote: >> So you don't want MAM users to be able to efficiently sync archives with >> multiple holes by a simple

Re: [Standards] Exact hint for Result Set Management

2018-07-12 Thread Ненахов Андрей
чт, 12 июл. 2018 г. в 15:26, Matthew Wild : > What you are describing - a local archive with multiple holes that the > implementation is unaware of - is not a state that I see any such > optimal correctly implemented MAM usage getting into. Actually, it's a typical state if a server has

Re: [Standards] Exact hint for Result Set Management

2018-07-12 Thread Florian Schmaus
On 12.07.2018 12:39, Kevin Smith wrote: > On 12 Jul 2018, at 11:23, Matthew Wild wrote: >> >> On 11 July 2018 at 18:25, Florian Schmaus wrote: >>> On 11.07.2018 18:01, Matthew Wild wrote: On 11 July 2018 at 16:33, Florian Schmaus wrote: > I recently submitted PR #672 to the xeps repo

Re: [Standards] Exact hint for Result Set Management

2018-07-12 Thread Kevin Smith
On 12 Jul 2018, at 11:23, Matthew Wild wrote: > > On 11 July 2018 at 18:25, Florian Schmaus wrote: >> On 11.07.2018 18:01, Matthew Wild wrote: >>> On 11 July 2018 at 16:33, Florian Schmaus wrote: I recently submitted PR #672 to the xeps repo https://github.com/xsf/xeps/pull/672

Re: [Standards] Exact hint for Result Set Management

2018-07-12 Thread Matthew Wild
On 11 July 2018 at 18:25, Florian Schmaus wrote: > On 11.07.2018 18:01, Matthew Wild wrote: >> On 11 July 2018 at 16:33, Florian Schmaus wrote: >>> I recently submitted PR #672 to the xeps repo >>> >>> https://github.com/xsf/xeps/pull/672 >>> >>> to make users of RSM, like MAM, aware whether the

Re: [Standards] Exact hint for Result Set Management

2018-07-11 Thread Florian Schmaus
On 11.07.2018 18:01, Matthew Wild wrote: > On 11 July 2018 at 16:33, Florian Schmaus wrote: >> I recently submitted PR #672 to the xeps repo >> >> https://github.com/xsf/xeps/pull/672 >> >> to make users of RSM, like MAM, aware whether the result is exact or >> not. It received some scepticism

Re: [Standards] Exact hint for Result Set Management

2018-07-11 Thread Matthew Wild
On 11 July 2018 at 16:33, Florian Schmaus wrote: > I recently submitted PR #672 to the xeps repo > > https://github.com/xsf/xeps/pull/672 > > to make users of RSM, like MAM, aware whether the result is exact or > not. It received some scepticism from the council members in today's > council

[Standards] Exact hint for Result Set Management

2018-07-11 Thread Florian Schmaus
I recently submitted PR #672 to the xeps repo https://github.com/xsf/xeps/pull/672 to make users of RSM, like MAM, aware whether the result is exact or not. It received some scepticism from the council members in today's council meeting. I am to blame here as I thought the abstract motivation in