22
edits
Difference between revisions of "PubSubIssues"
Jump to navigation
Jump to search
→No text on #publish_model
| (2 intermediate revisions by one other user not shown) | |||
| Line 49: | Line 49: | ||
confusing, too. I'd rather go with talking about 'retracting items' and | confusing, too. I'd rather go with talking about 'retracting items' and | ||
'deleting nodes' thoughout, and not talk about 'deleting items'. | 'deleting nodes' thoughout, and not talk about 'deleting items'. | ||
</blockquote> | |||
<blockquote> | |||
I think that many (all?) clients ignore this feature for discovery | I think that many (all?) clients ignore this feature for discovery | ||
altogether, so what about making 'delete-items' a thing that servers | altogether, so what about making 'delete-items' a thing that servers | ||
| Line 55: | Line 57: | ||
depend on 'retract-items' exclusively? | depend on 'retract-items' exclusively? | ||
</blockquote> | </blockquote> | ||
=== No text on #publish_model === | |||
A few examples mention an option #publish_model, which seems useful, but there's no actual text describing behaviour of said option. | |||
=== Entity node creation authorization request (Section 8.1) === | |||
There's no way to know if an entity can create (or not) a node before actually create it. | |||
This issue bring a bad UI experience on some Pubsub clients (we display an error after the form creation submission). | |||
== XEP-0163: PEP == | == XEP-0163: PEP == | ||