#1263 net.connect should have greater control for when to consider a connection successful
Reporter
Zash
Owner
Nobody
Created
Updated
Stars
★ (1)
Tags
Type-Enhancement
Priority-Medium
Milestone-0.12
Status-Accepted
Zash
on
If net.connect is to replace mod_s2s/s2sout.lib there should be more control over when to consider an individual connection attempt as failed and proceed to the next IP address or SRV target.
Currently the attempts stop once one connection is connected (when listeners.onconnect is called). XMPP s2s connections would benefit from delaying this until a stream has been opened by the remote, to be sure that it really is something that speaks XMPP there.
Zash
on
https://hg.prosody.im/trunk/rev/64cfa396bb84 fixed something related to this, wherein listeners.onconnect was called for a failed connection attempt, halting net.connect and preventing it from continuing with other targets.
If net.connect is to replace mod_s2s/s2sout.lib there should be more control over when to consider an individual connection attempt as failed and proceed to the next IP address or SRV target. Currently the attempts stop once one connection is connected (when listeners.onconnect is called). XMPP s2s connections would benefit from delaying this until a stream has been opened by the remote, to be sure that it really is something that speaks XMPP there.
https://hg.prosody.im/trunk/rev/64cfa396bb84 fixed something related to this, wherein listeners.onconnect was called for a failed connection attempt, halting net.connect and preventing it from continuing with other targets.