Difference between revisions of "XEP-Remarks/XEP-0060: PubSub"
Jump to navigation
Jump to search
(Add Category) |
(Reliability issues) |
||
| Line 1: | Line 1: | ||
= Reliability issues = | |||
https://mail.jabber.org/pipermail/standards/2019-October/036503.html | |||
Is there a way to know as a client when we're going to run into the | |||
limit [of items]? Or when we've gone over the limit? Or is the pubsub | |||
service just overwritting stuff and nobody ever noticies? | |||
= No mechanism to query all items after an item with a certain ID = | = No mechanism to query all items after an item with a certain ID = | ||
Revision as of 20:22, 31 March 2020
Reliability issues
https://mail.jabber.org/pipermail/standards/2019-October/036503.html
Is there a way to know as a client when we're going to run into the limit [of items]? Or when we've gone over the limit? Or is the pubsub service just overwritting stuff and nobody ever noticies?
No mechanism to query all items after an item with a certain ID
This makes it hard and very inefficient to catch up on a PubSub node, after an client comes online again.
XMPP address of publisher is not included in the notification
Sometimes you want to know who actually published the item.