Understood. I may take the time to look at the Jabber Component XEP a bit more and see about fleshing it out some. The XSD shows presence but it doesn't really discuss how presence is shared. For client's, presence is related to a roster. I suppose there is nothing stopping you from subscribing directly to a components presence. I haven't tried this as I have been relying on OpenFire. The OpenFire gui doesn't provide the means to setup a roster for a component. I will need to try to subscribe to it directly and see how that works.
Todd Herman -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Peter Saint-Andre Sent: Tuesday, May 29, 2012 10:38 PM To: XMPP Standards Subject: Re: [Standards] UPDATED: XEP-0267 (Server Buddies) On 5/29/12 8:33 PM, Todd Herman wrote: > Question: Can this extension (XEP-00267) used with Components? The > ability for components to send and receive presence is important to us > but the Jabber Component extension doesn't really expand on this much. > I believe they can receive presence information as, at least with > OpenFire, you can add a component to a roster but you can't do the > opposite (since components don't have an account or a roster). I am > wondering if the concepts discussed in 0267 could apply to a component > also. Thoughts? Any entity can share presence information with any other entity. So, yes, an add-on component could share presence with other components, with the server it's connected to, with users of the component, etc. For purposes of XEP-0267 I was interested only in server-to-server presence to used in improving federation of core XMPP servers, not components. Peter -- Peter Saint-Andre https://stpeter.im/
