Lines Matching refs:has
28 nonblocking socket. However, despite this, the B<SSL> object still has blocking
29 behaviour. When the B<SSL> object has blocking behaviour then this means that
41 has nonblocking behaviour. With a nonblocking B<SSL> object, functions such as
55 the application has to do, it must also be prepared to come back and retry the
57 complete. Ideally it would only do this in the event that something has changed
98 * whether the state of the underlying socket has changed or not.
109 * makes this demo block until it has something more useful to do. In a
118 * because of the timeout. If the 100ms GUI timeout has expired but the
119 * tvp timeout has not then go and update the GUI and then restart the
162 socket(s) to become readable/writeable or until the timeout has expired before
167 A QUIC application that has been configured for nonblocking behaviour will need
170 example because the stream has been reset or because the underlying connection
171 has failed), or non-fatal (for example because we are trying to read from the
172 stream but no data has not yet arrived from the peer for that stream).
179 out what type of error has occurred. If the error is non-fatal and can be
188 an B<SSL> object but the peer has indicated that it will not send any more data
194 the stream has been reset by the peer, or because the underlying connection has
199 stream, or whether the underlying connection has also failed. A return value
200 of B<SSL_STREAM_STATE_RESET_REMOTE> tells you that the stream has been reset by
202 connection has closed.
233 * The stream has been reset but the connection is still
