[Standards-JIG] JEP-60 Item id for node configuration change notifications
stpeter at jabber.org
Wed May 10 20:22:06 UTC 2006
-----BEGIN PGP SIGNED MESSAGE-----
Peter Saint-Andre wrote:
> Peter Saint-Andre wrote:
>>> Murat Bog wrote:
>>>>> According to section 8.2 of version 1.8pre17, when the node configuration
>>>>> changes, the server sens a notification to all subscribers. The
>>>>> notification will have an item element whose id attribute will be set to
>>>>> Since publishers are allowed to provide item ids, does this mean that the
>>>>> "configuration" value is reserved and can be generated by a server only? If
>>>>> so, there would be an implied requirement that a server is supposed to
>>>>> reject publications where the publisher has set the id attribute of item
>>>>> element to "configuration". If not, I don't see how a consumer can
>>>>> distinguish notifications due to configuration changes from publications
>>>>> unless another element type were defined for node configuration change
>>> I'm not sure why Peter did it that way, since that's the only reserved
>>> ItemID as far as I can see. However, I don't immediately see a better
>>> approach, so I think a service would in fact need to reject publication
>>> requests that specify an ItemID of "configuration" (i.e., reserve that
>>> ItemID for generation only by the service). I'll clarify that in the text.
> I've added the following note to Section 8.2 of my working copy:
> Note: The "configuration" ItemID MUST be reserved by a service; if an
> owner or publisher attempts to publish an item with an ItemID of
> "configuration", the service MUST either modify the ItemID before
> generating the associated notifications or refuse the publication
> request with a <conflict/> error.
On reflection, I think <not-allowed/> is the right error.
> I will also add an appropriate error flow to Section 7.1.
I propose the following text:
If the requesting entity specified a reserved ItemID, the service MUST
either modify the ItemID before generating the associated notifications
or refuse the publication request with a <not-allowed/> error, which
SHOULD also include a pubsub-specific error condition of
<itemid-reserved/>. Note: Currently the only reserved ItemID is
"configuration" as described in the Manage Subscription Requests section
of this document.
Example 88. Entity attempts to publish item with reserved ItemID
to='hamlet at denmark.lit/elsinore'
... PAYLOAD ...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 3641 bytes
Desc: S/MIME Cryptographic Signature
More information about the Standards