view idavoll/implementation_issues.txt @ 38:c9ddca3cce20

Change exception classes to include stanza error. Change name of exception base class to Error. Change backend error map to have a tuple as value: stanza-error, pubsub-error. Remove empty componentConnected() definition in Service. Move registering of notification from __init__ to componentConnected in ComponentServiceFromNotificationService. Add observers for subscribe, options and configure.
author Ralph Meijer <ralphm@ik.nu>
date Sun, 31 Oct 2004 16:03:50 +0000
parents 23b1dca64d06
children 0072fc44fca8
line wrap: on
line source

- What happens when a node creation request is accompanied by a configure
  node, but node configuration is not implemented?

  Solution:

  Reply with a not-acceptable stanza error, with a node-not-configurable
  error attached.

- Node purging with many items in storage and notification of retraction enabled
could produce a large number of notifications. Suggestion: instead send a
<event><purge/></event>

- Examples 58 and 62 are the same

- What error to return for outcast user requests?
  - What if some admin requested it?

- Why not return forbidden when JIDs do not match on subscription?

- What to do when receiving an unsubscription request with a subid, when
  subids are not supported? Ignore or reply with bad-request?

- unsubscription: why check for the requestor being subscribed. You want to
  check if the jid is subscribed. An not-authorized can be sent if the
  requestor and jid don't match. Otherwise, unexpected-request might
  be appropriate when the jid is not subscribed along with a special
  child element of not-subscribed in the pubsub#error namespace.