|
33
|
1 - What happens when a node creation request is accompanied by a configure
|
|
22
|
2 node, but node configuration is not implemented?
|
|
|
3
|
|
|
4 Solution:
|
|
|
5
|
|
|
6 Reply with a not-acceptable stanza error, with a node-not-configurable
|
|
|
7 error attached.
|
|
|
8
|
|
33
|
9 - Node purging with many items in storage and notification of retraction enabled
|
|
|
10 could produce a large number of notifications. Suggestion: instead send a
|
|
|
11 <event><purge/></event>
|
|
|
12
|
|
|
13 - Examples 58 and 62 are the same
|
|
|
14
|
|
|
15 - What error to return for outcast user requests?
|
|
|
16 - What if some admin requested it?
|
|
|
17
|
|
|
18 - Why not return forbidden when JIDs do not match on subscription?
|
|
36
|
19
|
|
|
20 - What to do when receiving an unsubscription request with a subid, when
|
|
|
21 subids are not supported? Ignore or reply with bad-request?
|
|
|
22
|
|
|
23 - unsubscription: why check for the requestor being subscribed. You want to
|
|
|
24 check if the jid is subscribed. An not-authorized can be sent if the
|
|
|
25 requestor and jid don't match. Otherwise, unexpected-request might
|
|
|
26 be appropriate when the jid is not subscribed along with a special
|
|
|
27 child element of not-subscribed in the pubsub#error namespace.
|
