As an Openfire developer, I can tell you that we find the naming "legacy" for "direct SSL" unfortunate. We're planning to rename that. Direct SSL. I happened to create an issue for that in our tracker yesterday: https://issues.igniterealtime.org/projects/OF/issues/OF-1378
On 23 September 2017 at 14:58, 殷啟聰 | Kai-Chung Yan <seamli...@gmail.com> wrote: > According to the documentations of some XMPP servers (e.g. OpenFire and > ejabberd), using TLS directly when connecting is described as "legacy", > "deprecated" or "not recommended". Is this "legacy" connection method the > same as the one described in this XEP? If so, is this XEP also encouraging > direct TLS unlike those servers? > > > Guus der Kinderen 於 2017年09月23日 02:08 寫道: > > > Wait, what are we discussing again? >> >> > We were discussing if I was fully, or completely right, of course. :-P > > Also, I again have to postpone my bikeshed-warming-party. It's not > finished yet. Will let you know. > > > _______________________________________________ > Standards mailing list > Info: https://mail.jabber.org/mailman/listinfo/standards > Unsubscribe: standards-unsubscr...@xmpp.org > _______________________________________________ > > > > _______________________________________________ > Standards mailing list > Info: https://mail.jabber.org/mailman/listinfo/standards > Unsubscribe: standards-unsubscr...@xmpp.org > _______________________________________________ > >
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org _______________________________________________
