| … | |
… | |
| 131 | |
131 | |
| 132 | The peer's numeric host and port (the socket peername) are passed as |
132 | The peer's numeric host and port (the socket peername) are passed as |
| 133 | parameters, together with a retry callback. At the time it is called the |
133 | parameters, together with a retry callback. At the time it is called the |
| 134 | read and write queues, EOF status, TLS status and similar properties of |
134 | read and write queues, EOF status, TLS status and similar properties of |
| 135 | the handle will have been reset. |
135 | the handle will have been reset. |
| 136 | |
|
|
| 137 | It is not allowed to use the read or write queues while the handle object |
|
|
| 138 | is connecting. |
|
|
| 139 | |
136 | |
| 140 | If, for some reason, the handle is not acceptable, calling C<$retry> will |
137 | If, for some reason, the handle is not acceptable, calling C<$retry> will |
| 141 | continue with the next connection target (in case of multi-homed hosts or |
138 | continue with the next connection target (in case of multi-homed hosts or |
| 142 | SRV records there can be multiple connection endpoints). The C<$retry> |
139 | SRV records there can be multiple connection endpoints). The C<$retry> |
| 143 | callback can be invoked after the connect callback returns, i.e. one can |
140 | callback can be invoked after the connect callback returns, i.e. one can |
