On 09/02/2022 12.17, Melvin Keskin wrote:
Hi,

I am wondering why the XML schema for PubSub events (
https://xmpp.org/extensions/xep-0060.html#schemas-event) specifies that
the "items" element of events may contain multiple "item" and "retract"
elements:

<xs:element name='items'>
   <xs:complexType>
     <xs:choice>
       <xs:element ref='item' minOccurs='0' maxOccurs='unbounded'/>
       <xs:element ref='retract' minOccurs='0' maxOccurs='unbounded'/>
     </xs:choice>
     <xs:attribute name='node' type='xs:string' use='required'/>
   </xs:complexType>
</xs:element>

While
https://xmpp.org/extensions/xep-0060.html#publisher-publish-request
and https://xmpp.org/extensions/xep-0060.html#publisher-delete-request
  specify that it is not allowed to publish multiple items,
https://xmpp.org/extensions/xep-0060.html#impl-batch allows that
explicitly.

I could imagine an event containing multiple items triggered after such
a batch processing or if the server caches multiple single item
publications before sending an event notification. But if that should
be possible and handled by clients, where is that specified?

Yes, the confusion is understandable. Working up to version 1.13, batch processing was first removed [1] and then restored [2], pending discussion. It seems the restoration was not complete in all places, including sections 7.1 and 7.2.

[1] <https://github.com/xsf/xeps/commit/8aa0f950db1e8036c8a0c4eab898cc8e0d7121c4> [2] <https://github.com/xsf/xeps/commit/d47e3746f9ebe18e6deeccffe2131bf9848514ce>

It seems to me this is an editorial oversight, and discussion didn't result in a final removal. It would be good to understand if implementations currently support batch processing, though.

I know that both Wokkel and Idavoll do support batch processing, but that's not significant enough to be representative for all implementations.

--
ralphm
_______________________________________________
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
_______________________________________________

Reply via email to