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

Brian Cully bcully at gmail.com
Wed Nov 15 13:30:10 UTC 2017

On November 15, 2017 at 03:59:46, Ruslan N. Marchenko (me at ruff.mobi) wrote:
> On 14.11.2017 22:37, Sam Whited wrote:
> >
> > What do the server devs here think?
> >
> >
> To be fair this protocol is implemented in majority(?) of existing xmpp
> server implementations so the burden is zero.
> The question is rather - what is the future vision for this component
> protocol? It considered as a necessary communication method for new
> external services or s2s with all the new features (like bidi) is
> sufficient making this one redundant. My personal answer is - go S2S.
> But at the same time i'm not doing much of component development
> therefore cannot say whether XEP-0114 is really resolving some corner
> cases hence being irreplaceable.

	It’s not that 0114 isn’t irreplaceable, that I can see, it’s that
it’s dead simple to implement and debug. IMHO, it’s a fairly low
burden for server devs, and a positive boon for component devs, since
there’s just so much less that has to be worried about vs. s2s. In
addition, there are a fair number of extant components out there that
Just Work™.


More information about the Standards mailing list