[jdev] How to determine if pubsub sends publisher JID in events?

[Peter Saint-Andre]

On 11/2/10 2:20 PM, Sergey Dobrov wrote:
> On 11/03/2010 02:06 AM, Peter Saint-Andre wrote:
>> On 11/2/10 2:02 PM, Sergey Dobrov wrote:
>>> On 11/03/2010 01:56 AM, Peter Saint-Andre wrote:
>>>> On 10/30/10 7:27 AM, Sergey Dobrov wrote:
>>>>> I have a problem with interpretation of 7.1.2.3 paragraph of XEP-60. It
>>>>> says: "If configured to do so, the service can include the pubisher of
>>>>> the item when it generates event notifications." How can I determine if
>>>>> server will publish my JID to choose right pubsub service for publish?
>>>>> This is not a node configuration field?
>>>>
>>>> I think this is handled via the "pubsub#itemreply" field, set to a value
>>>> of "publisher". But that's not very clear in the spec.
>>> No, pubsub#itemreply decides if we should to replace true publisher to
>>> the owner of a node. But there are no way to switch on such
>>> notifications. That's really bad for me. Can we do with this something?
>>
>> http://xmpp.org/extensions/xep-0060.html#impl-association
>>
>> Perhaps "itemreply" is not a good name for it, but basically this node
>> configuration option set to "publisher" tells the service to always
>> include the publisher's JID in the item. I think that's what you want,
>> right?
> Yeah, that's right behavior but it's not clear yet. You mean that if
> node's configuration form has "itemreply" field then a pubsub service
> will ALWAYS put information about publisher? So, in this case
> "publisher" attribute can't be switched off? Because there are no such
> option.

Node configuration updates are always the complete config, so if you
want to turn it off just leave the itemreply option out of the x-data
form that you upload to the server.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6105 bytes
Desc: S/MIME Cryptographic Signature
URL: <https://www.jabber.org/jdev/attachments/20101102/be490bc0/attachment.bin>