I tried with Prosody 0.9.12 today and found that it has the same behavior as ejabberd. I guess that "Resource Binding indicating stream negotiation" has been a consensus among developers. I personally do not think this is good, because clients who strictly comply with RFC 6120 will have trouble talking to the rest of the world.
Peter Saint-Andre 於 2017/8/16 上午11:32 寫道: > On 8/15/17 9:18 PM, 殷啟聰 wrote: >> @Kim >> >> Yes I noticed that note, though I believe the "exception" means "must >> not send stanza before completing stream negotiation except for Resource >> Binding" rather than "send a <features/> element after negotiating every >> feature except Resource Binding". > That's my interpretation, as the author. :-) However, it could have been > worded more clearly. > > Peter > > > _______________________________________________ > JDev mailing list > Info: https://mail.jabber.org/mailman/listinfo/jdev > Unsubscribe: [email protected] > _______________________________________________
signature.asc
Description: OpenPGP digital signature
_______________________________________________ JDev mailing list Info: https://mail.jabber.org/mailman/listinfo/jdev Unsubscribe: [email protected] _______________________________________________
