[Standards-JIG] new disco#publish-info feature

Ralph Meijer jabber.org at ralphm.ik.nu
Tue Sep 27 14:04:24 UTC 2005

On Sat, Jul 23, 2005 at 06:40:24PM +0100, Ian Paterson wrote:
> Peter St Andre wrote in his blog on 2005-02-28:
> > Publish the key to a well-known service discovery node
> > using the "disco publish" protocol defined in JEP-0030
> Yes, this would be nice, but I'm not sure how JEP-0030 enables it?
> AFAICT The disco#publish feature only explicitly enables an entity to
> modify the *list of items* that will appear in its server's responses to
> disco#items queries (for any node of the entity's bare JID).
> IMHO an equivalent ability to modify the content of the 'jabber:x:data'
> element within disco#info query results would be a simple and generally
> useful 'protocol building block' for publishing relatively static data
> associated with a specific bare JID. (See JEP-0045 Example 7 "Room
> Returns Extended Disco Info Results" for an example of an extended
> disco#info result.)
> Pubsub is of course more suitable whenever data is not associated with a
> JID or when change notifications are required - especially if the data
> may be updated regularly.
> I understand that JEP-0030 is Final, and unless I've completely missed
> something, a new JEP would be required to document the protocol (see the
> examples for publishing long-term public signature-verification keys
> below).
> Perhaps the extra functionality would also encourage more disco publish
> implementations. :)

Indeed, the disco#info data is currently read-only, and what you propose
might be a nice addition. However, some of the fields in the disco
extension might be automatically generated.

For publish-subscribe, you can do a disco#info query on a node and get
the node's meta data, which may include fields that are set using node
configuration (e.g. whether the node persists items) and other fields
(e.g. the creation date of the node).

How would you solve this generically?



More information about the Standards mailing list