> I'd rather focus on getting a successor, possibly xep0255, out of the > door. And if we see that major components (spectrum2 comes to my > mind) > and servers support the successor, we could consider removing xep0114 > from the compliance suite. But not before that has happened.
This seems like a reasonable position, other than I think it's XEP- 0225. For what its worth I was trying to write a gateway using the component protocol. 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 Diane
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org _______________________________________________
