Re: [Standards] xep-0313 missing features

if you set both it goes forwards (from old to new)? how to set direction explicitly in such case? On Tue, Mar 6, 2018 at 2:19 PM, Kevin Smith wrote: > On 6 Mar 2018, at 13:14, Jonas Wielicki wrote: > > I think it would be great to have a way to limit

Re: [Standards] xep-0313 missing features

Conclusion: 1. it is not possible to iterate efficiently backwards by including both & in the query because once is included in the query then it iterates forwards. that means when iterating backwards client has to omit and fetch entire pages and then the last page will mostly overlap with some

Re: [Standards] xep-0313 missing features

yes thats what i thought - carbon would be good On Mon, Mar 5, 2018 at 6:14 PM, Kevin Smith <kevin.sm...@isode.com> wrote: > On 5 Mar 2018, at 16:42, Lazar Otasevic <redhotb...@gmail.com> wrote: > > @Philipp BTW, how do you handle own messages? how does client discover &g

Re: [Standards] xep-0313 missing features

g message https://xmpp.org/ > extensions/xep-0359.html > > if you request later the archive and discover a origin-id you can check > your db if it is already present > > > > 2018-03-05 17:42 GMT+01:00 Lazar Otasevic <redhotb...@gmail.com>: > >> @Philipp BTW, ho

Re: [Standards] xep-0313 missing features

@Philipp BTW, how do you handle own messages? how does client discover archived id for newly sent message? On Mon, Mar 5, 2018 at 4:48 PM, Lazar Otasevic <redhotb...@gmail.com> wrote: > Kevin suggested to use both (before..after) and i see no way to query > first 10 or last 10, its

Re: [Standards] xep-0313 missing features

ng to get the last 10 from a JID or the last 10 inside a > timeframe > > 2018-03-05 14:06 GMT+01:00 Lazar Otasevic <redhotb...@gmail.com>: > >> because, why not. clients should be able to choose direction i guess. not >> every needs to work the same? >> >> On Mon,

Re: [Standards] xep-0313 missing features

does response has to return count? On Mon, Mar 5, 2018 at 2:06 PM, Lazar Otasevic <redhotb...@gmail.com> wrote: > because, why not. clients should be able to choose direction i guess. not > every needs to work the same? > > On Mon, Mar 5, 2018 at 1:56 PM, Philipp Hörist &l

Re: [Standards] xep-0313 missing features

because, why not. clients should be able to choose direction i guess. not every needs to work the same? On Mon, Mar 5, 2018 at 1:56 PM, Philipp Hörist wrote: > > 2018-03-05 13:42 GMT+01:00 Lazar : > >> yes we need explicit controll to request last 10

Re: [Standards] xep-0313 missing features

Kevin says we can :) I asked him to clarify... we'll see. On Mon, Mar 5, 2018 at 11:45 AM, Philipp Hörist wrote: > >> >> You can already fill holes with the current spec, by specifying both >> and on the RSM query can’t you? If that doesn’t >> obviously follow from the

Re: [Standards] xep-0313 missing features

isode.com> wrote: > On 4 Mar 2018, at 22:01, Lazar Otasevic <redhotb...@gmail.com> wrote: > >> I really don't understand this argument. Doing a MAM query is exactly > >> like fetching a list of ids, except that you also get the content as > >> well. As I m

Re: [Standards] xep-0313 missing features

See my answer to Mathew, maybe i clarified better. cu On Sun, Mar 4, 2018 at 9:08 PM, Philipp Hörist <phil...@hoerist.com> wrote: > > 2018-03-04 18:37 GMT+01:00 Lazar Otasevic <redhotb...@gmail.com>: > >> Phillip, >> >> I feel like we dont entirely unde

Re: [Standards] xep-0313 missing features

> > > > Matthew, > > I really don't understand this argument. Doing a MAM query is exactly > like fetching a list of ids, except that you also get the content as > well. As I mentioned, I see no case in which you would want the ids > and not the content. Even if you get the ids, you will fetch the

Re: [Standards] xep-0313 missing features

ients must treat as opaque strings (e.g. there is no requirement for them > to be numeric, sequenced or GUIDs) > > > 2018-03-03 23:53 GMT+01:00 Lazar Otasevic <redhotb...@gmail.com>: > >> Hi, I think I miss some features here: >> >> 1. fetching messages by giving a s

Re: [Standards] xep-0313 missing features

e features were kind of existent back in 2005 in xep-0013. Now we removed those features, why? Thanks On Sun, Mar 4, 2018 at 4:36 PM, Matthew Wild <mwi...@gmail.com> wrote: > Hi Lazar, > > On 3 Mar 2018 22:54, "Lazar Otasevic" <redhotb...@gmail.com> wrote: >

[Standards] xep-0313 missing features

Hi, I think I miss some features here: 1. fetching messages by giving a set of ids, also similar like xep-013 Fetching message by id(s) is needed for example when i have a custom push notification with a given message id(s) and client needs to get that one message asap and show it in the chat.