[Standards] LAST CALL: XEP-0387 (XMPP Compliance Suites 2017)

Arc Riley arcriley at gmail.com
Fri Nov 10 06:26:37 UTC 2017


On Thu, Nov 9, 2017 at 5:00 PM, Diane Trout <diane at ghic.org> wrote:

> Also a better justification for the component protocol is that it
> allows people to develop reasonably portable new features like xep 363.
> https://github.com/siacs/HttpUploadComponent


I agree with you that being able to implement a new feature with a
server-agnostic codebase is a cool feature.

However, XEP-0114 does not cover the ability to have an external process
add support for a new XEP. That is certainly a feature that many modern
XMPP servers support, but AFAIK that protocol has never been documented in
a XEP - certainly not this one.

Further, there's absolutely valid reasons why an author may not want to
support it (eg, security).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/standards/attachments/20171109/f7f09973/attachment.html>


More information about the Standards mailing list