[Standards-JIG] JEP-60 Item id for node configuration change notifications

Peter Saint-Andre stpeter at jabber.org
Wed May 10 19:14:34 UTC 2006


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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 
> "configuration".
> 
> 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 
> notifications.

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.

Peter

- --
Peter Saint-Andre
Jabber Software Foundation
http://www.jabber.org/people/stpeter.shtml

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEYjuaNF1RSzyt3NURAkHeAJ94Js7VSR6tALC5byZ56f60tbqaKwCeLPfI
ti7GMggJidUZVJ54r5AqoE0=
=7j1t
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3641 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20060510/28361aa3/attachment.bin>


More information about the Standards mailing list