mirror of
https://github.com/bjc/prosody.git
synced 2025-04-03 05:07:42 +03:00
814817ebf2
Normally with bidi, any outgoing connection should be the same as the incoming, hence when closing a bidi connection it should be removed as a route to the remote server. However it is not guaranteed, a remote bidi-capable server might have decided to open a new connection for some reason. This can lead to a situation where there are two bidi connections, and the s2sout route is a locally initiated s2sout connection. In this case, such a s2sout connection should be kept. Noticed in a rare case where bidi has just been enabled on a running server, and something establishes new connections immediately when a connection is closed. |
||
|---|---|---|
| .. | ||
| certmanager.lua | ||
| configmanager.lua | ||
| features.lua | ||
| hostmanager.lua | ||
| loggingmanager.lua | ||
| moduleapi.lua | ||
| modulemanager.lua | ||
| portmanager.lua | ||
| rostermanager.lua | ||
| s2smanager.lua | ||
| sessionmanager.lua | ||
| stanza_router.lua | ||
| statsmanager.lua | ||
| storagemanager.lua | ||
| usermanager.lua | ||