Hello > This specification defines a way for an XMPP entity to announce the limits it will enforce for data received on a stream. > > URL: https://xmpp.org/extensions/inbox/xep-sla.html
This is a sorely needed extension. However, the proposal does not solve the more general problem of knowing the limitations when you communicate with another, only the size and time limits between immediately connected entities. A sender (client1) who needs to send something to another client (client2) passes one or two brokers (broker[1, broker2]), each one in this path might have different size limitations. A notification in the stream element does not resolve this more general problem. Furthermore, being constantly advertised in every request, creates a lot of extra bytes being communicated, with not added value, as the information is only needed once per limitation (best case). Would it not be better with a statement in a service discovery response? There, each server/component/client can declare their limitations. Any change in limitation would change the hash in entities capabilities, which is already sent. So a change would be detected by all participants, without the added bytes each time an entity connects. Also, a service discovery mechanism, would allow an entity to query all participants in a route, to figure out what the limitations are along that particular route. Best regards, Peter Waher
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org _______________________________________________
