|
Hey, it seems that the pubsub list is dead and that pubsub discussion
is happening here instead. Sorry to anyone who receives this message
twice. - Eric -------- Original Message --------
Hey everyone, I'm working on a project using pubsub/pep and have a few questions. Should pep nodes be returned in the result of a disco#items query on a bare JID? Section 5.2 of XEP-0060 makes it sound like this should be the case, but it's not completely clear, and ejabberd does not return them. If not, what's the correct way to get a list of your pep nodes? Affiliations request? XEP-0163 section 6.1 says that a PEP server should return the pubsub<feature>s on behalf of a user for a disco#info request, however ejabberd 2.0.2_2 does not. Is this an implementation bug, or am I misunderstanding the specifications? Here's what I do get: <iq to='[email protected]' id='disco1' type='get'> <query xmlns='http://jabber.org/protocol/disco#info'/> </iq> <iq from="[email protected]" type="result" to="[email protected]/Psi" id="disco1" > <query xmlns="http://jabber.org/protocol/disco#info"> <identity category="pubsub" type="pep" /> <feature var="vcard-temp" /> <feature var="http://jabber.org/protocol/commands" /> </query> </iq> How are clients expected to behave when they see a pubsub/pep <identity>? What's the purpose of this, assuming you also get pubsub-related <feature>s? XEP-0060 mentions that events can be "transient" or "persistent", could someoe please clarify what these are? I didn't find it very clear, though I may have missed the definitions. Thanks! - Eric |
- [Standards] [Fwd: [PubSub] Questions about pubsub/pep] Eric Butler
