I'm not seeing what the compare part of this proposal actually is.
Unless I misunderstand, it simply publishes the item only if it will update an existing one. If that is the case, I would propose a small change to the existing spec to add an attribute to the <item> element that enables this functionality would be far simpler, and less prone to mistakes like setting the item id to something other than the proposed prevId. <item id='1' replace = 'true'> where replace (or some other better named attribute) is optional and defaults to false. ________________________________ From: Standards <[email protected]> on behalf of Jonas Wielicki <[email protected]> Sent: August 24, 2017 8:10 AM To: [email protected] Subject: [Standards] Proposed XMPP Extension: Atomically Compare-And-Publish PubSub Items The XMPP Extensions Editor has received a proposal for a new XEP. Title: Atomically Compare-And-Publish PubSub Items Abstract: This specification provides a mechanism to atomically Compare-And- Publish items to a PubSub node. URL: https://xmpp.org/extensions/inbox/cap.html The Council will decide in the next two weeks whether to accept this proposal as an official XEP. _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Standards Info Page - mail.jabber.org Mailing Lists<https://mail.jabber.org/mailman/listinfo/standards> mail.jabber.org Your email address: Your name (optional): You may enter a privacy password below. This provides only mild security, but should prevent others from messing with ... Unsubscribe: [email protected] _______________________________________________
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
