jdev - 2024-08-10

am I seeing this right that XEP-0114 does not use RFC 6120 XML streams?

in particular, it seems to violate "after sending the response stream header the receiving entity MUST send a <features/> child element" from RFC 6120 §4.3.2

It does that

You may notice the Historical status, suggesting it predates the RFC process :)

I think https://xmpp.org/extensions/xep-0225.html was the intended replacement, but it hasn't moved much

okay, thanks

i learn for deep

i dont understand the server connection

Can help me ?

You are a server that supports bidi ( https://xmpp.org/extensions/xep-0288.html ), you get 2 incoming s2s connections from example.org (maybe multiple nodes in a cluster... Doesn't matter why), they both enable bidi... Now you have 2 outgoing streams for messages to example.org... which do you send messages out? Or duplicate messages to both 😈 ? Does anything specify this? cc dwd

You will close one of them. Race condition means effectively random which one.

You can't be connected twice so the second connection should boot the first one

Sure you can be connected twice or more

Yes you can be connected *to* multiple times (multiple incoming s2s), but until bidi, you controlled how many outgoing connections you made, with bidi you don't though...

You still do though. You're not required to allow this multiple outs case. Can close one. Or possibly even reply with error to the bidi enable?

In case of a cluster that for some reasons opens one connection per node, wouldn't it be a waste of resources to close the other connections?

At least if it just reconnects again from each node.