[Standards] publish+configure again

Peter Saint-Andre stpeter at jabber.org
Fri Mar 30 15:44:32 UTC 2007

Maciek Niedzielski wrote:
> Pedro Melo wrote:
>>> Item is not broadcasted only when publishing. The last item is saved and
>>> sent again when - for example - new subscriber becomes online.
>>> Now, if node configuration is changed after publishing (just changed, by
>>> using normal node configuration use case, not by p+c), and then someone
>>> in your roster becomes online, PEP service will send the last item to it
>>> if new configuration allows it, even if configuration at the moment of
>>> publishing did not. At least this is how I understand it. So as long as
>>> it is possible to configure a node without publishing new item that
>>> replaces old one, p+c won't work.
>> I'm used to other systems of pubsub in which the item behaves with the
>> configuration at the time of publishing. And it seems that PEP is
>> clearly not like that, hence my difficulties.
>> Thanks for the clarification, I'll see what this fact does for my client.
> Please note "At least this is how I understand it". I'm not PubSub
> expert, but I think this is how it works. However, I think that if
> misunderstood, someone from this the huge group of people wanting to
> kill all my arguments would have already corrected me ;)


I raised this issue in one of the Council meetings IIRC. If you think 
that p+c gives you complete control over who has access to the item for 
all time, you are mistaken.


Peter Saint-Andre
XMPP Standards Foundation

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 7358 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20070330/8a35c987/attachment.bin>

More information about the Standards mailing list