Le dimanche 13 janvier 2019, 12:53:51 CET Evgeny a écrit :
> On Sun, Jan 13, 2019 at 2:40 PM, Goffi wrote:
> > Future XEPs may extend this, but in case where it's too complicated,
> > implementation has always the choice to not implement it, or to have
> > different features with different
On Sun, Jan 13, 2019 at 2:40 PM, Goffi wrote:
Future XEPs may extend this, but in case where it's too complicated,
implementation has always the choice to not implement it, or to have
different features with different backends.
I really don't see how this will work in practice.
1) a client
Le dimanche 13 janvier 2019, 12:28:09 CET Evgeny a écrit :
> On Sun, Jan 13, 2019 at 2:16 PM, Goffi wrote:
> > For Pubsub services based on SQL or NoSQL databases, it should not be
> > too hard to implement as ordering is most of time a part of API.
>
> Note however, that some NoSQL databases
Le dimanche 13 janvier 2019, 12:24:45 CET Evgeny a écrit :
> On Sun, Jan 13, 2019 at 2:16 PM, Goffi wrote:
> > a XEP for XPATH like syntax
>
> And the server will process this XPATH query?
> Not sure if you're serious...
This is a future plan, not concerning the current proposal, and will be
On Sun, Jan 13, 2019 at 2:16 PM, Goffi wrote:
For Pubsub services based on SQL or NoSQL databases, it should not be
too hard to implement as ordering is most of time a part of API.
Note however, that some NoSQL databases only support a single index
in the query, DynamoDB is such an example.
On Sun, Jan 13, 2019 at 2:16 PM, Goffi wrote:
a XEP for XPATH like syntax
And the server will process this XPATH query?
Not sure if you're serious...
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe:
Hello,
I've read the council logs, I'll try to defend the protoXEP here (in addition
to what has already been said in this thread).
> it's a very specific use case, and it defines two hard-coded properties to
> order by. A clean approach would allow ordering by any field of the items,
>
On Sonntag, 13. Januar 2019 11:41:01 CET Goffi wrote:
> Le samedi 12 janvier 2019, 20:50:25 CET Jonas Schäfer a écrit :
> > […]
> > The lack of clock synchronisation is a problem in any case, even when the
> > timestamps are generated on the server side, since XMPP is federated. I’d
> > even argue
Le samedi 12 janvier 2019, 20:50:25 CET Jonas Schäfer a écrit :
> They do, here’s how: You have two metadata fields, let’s call them Time and
> Author. You have the following data:
>
> Time Author Item ID
> 10:00 Alice1
> 11:00 Alice2
> 12:00 Bob 3
> 13:00 Bob 4
> 14:00
For the council record: I’m +1 on this. I think it is useful as-is already. I
would like to see where this goes. I could imagine generalising the protocol
to be useful with all types of result sets (e.g. disco#items on MUC).
kind regards,
Jonas
signature.asc
Description: This is a digitally
On Montag, 7. Januar 2019 19:33:21 CET Goffi wrote:
> Hi Jonas,
>
> Le lundi 7 janvier 2019, 18:08:25 CET Jonas Schäfer a écrit :
> > On Sonntag, 6. Januar 2019 15:16:43 CET Jonas Schäfer wrote:
> > > Title: Order-By
> > > Abstract:
> > > This specification allows to change order of items
Le lundi 7 janvier 2019, 21:00:42 CET Evgeny a écrit :
> On Mon, Jan 7, 2019 at 8:28 PM, Goffi wrote:
> > Are you talking about the fact that "date of modification" (as
> > defined in the protoXEP) could be out of sync between clusters?
>
> No, from the discussion I thought you want to have
On Mon, Jan 7, 2019 at 8:28 PM, Goffi wrote:
Are you talking about the fact that "date of modification" (as
defined in the protoXEP) could be out of sync between clusters?
No, from the discussion I thought you want to have something like
incremental
unique "order" attribute in the node.
And
On Mon, Jan 07, 2019 at 11:30:26AM +0300, Evgeny wrote:
> On Mon, Jan 7, 2019 at 10:44 AM, Goffi wrote:
> > Is there any implementation in the wild which would have issue with node
> > order?
>
> Sure, any clustered database will have issues with
> such naive approach: after partitioning during
Hi Jonas,
Le lundi 7 janvier 2019, 18:08:25 CET Jonas Schäfer a écrit :
> On Sonntag, 6. Januar 2019 15:16:43 CET Jonas Schäfer wrote:
> > Title: Order-By
> > Abstract:
> > This specification allows to change order of items retrieval in a
> > Pubsub or MAM query
>
> Couple notes:
>
> - The
Hi Evgeny,
Le lundi 7 janvier 2019, 09:30:26 CET Evgeny a écrit :
> On Mon, Jan 7, 2019 at 10:44 AM, Goffi wrote:
> > Is there any implementation in the wild which would have issue with
> > node order?
>
> Sure, any clustered database will have issues with
> such naive approach: after
On Sonntag, 6. Januar 2019 15:16:43 CET Jonas Schäfer wrote:
> Title: Order-By
> Abstract:
> This specification allows to change order of items retrieval in a
> Pubsub or MAM query
Couple notes:
- The strings for the "modification" and "creation" fields (as used in the
element) should be URNs,
On Mon, Jan 7, 2019 at 10:44 AM, Goffi wrote:
Is there any implementation in the wild which would have issue with
node order?
Sure, any clustered database will have issues with
such naive approach: after partitioning during merge
you'll end up with duplicated orders, like 2 items
with
Hi Philipp,
thanks for your feedbacks
> - There is an attr missing that defines if the order should be ascending or
> descending, just order by creation is not specific enough to me.
>
> - There is a part where it says with RSM you can change the order. This is
> kind of wrong. With RSM you can
Hi,
Few things i noticed while reading
- There is an attr missing that defines if the order should be ascending or
descending, just order by creation is not specific enough to me.
- There is a part where it says with RSM you can change the order. This is
kind of wrong. With RSM you can in a
Le dimanche 6 janvier 2019, 15:16:43 CET Jonas Schäfer a écrit :
> The XMPP Extensions Editor has received a proposal for a new XEP.
>
> Title: Order-By
> Abstract:
> This specification allows to change order of items retrieval in a
> Pubsub or MAM query
>
> URL:
The XMPP Extensions Editor has received a proposal for a new XEP.
Title: Order-By
Abstract:
This specification allows to change order of items retrieval in a
Pubsub or MAM query
URL: https://xmpp.org/extensions/inbox/order-by.html
The Council will decide in the next two weeks whether to accept
22 matches
Mail list logo
