Le dimanche 13 janvier 2019, 12:53:51 CET Evgeny a écrit :
> On Sun, Jan 13, 2019 at 2:40 PM, Goffi <[email protected]> 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 issues a request with "direction"/whatever attribute
> 2) a server responds with "not-implemented" or some such
> 3) a client gets stuck? or should it re-send a modified request?
Well clients already have to manage different feature set. It's more:
1) client discover features of pubsub service
2) a) if server do ordering, fine, we do optimal workflow
b) if server doesn't support ordering, we can either show items in the not
optimal order (bad UX but it works),
or show a warning of whatever. This is a client decision and probably
depends of the context.
It's already the case for nearly every XMPP feature.
For instance most pubsub services don't currently support MAM filtering. If
it's available, nice you can click on categories to see filtered items, else
you can't do that.
In the same spirit, if other client doesn't support video, or e2ee, or
whatever, you have to adapt.
> Second problem is that competition in servers is quite high
> and if customers/users want the feature then I have to implement it
> somehow.
> That has happened in the past already.
If there is a high demand for a feature, there is probably a real need.
I don't find this is a good reason to not implement something, quite the
opposite actually.
> Third problem is assuming SQL-only backend to support the
> feature is the wrong approach, in my opinion.
This is not assuming SQL only backend at all. You can even implement quite
easily this XEP with flat files backend, you just have to keep a list of items
ids ordered by creation date, which is trivial to do.
++
Goffi
_______________________________________________
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: [email protected]
_______________________________________________
