Lines Matching refs:not
32 (although a connection with zero streams is probably not very useful, so
37 in the order that it was sent within that stream. The same is not true across
49 functions are thread safe, but the B<SSL> object is not. This means that you can
72 It is recommended that new multi-stream applications should not use a default
91 a remotely initiated stream. If the peer has not initiated any then this call
99 is not relevant if the default stream has been disabled as described in
103 then the initiator can write to it but not read from it, and vice-versa for the
114 In the event of one of these functions not returning a success code then
135 L<SSL_free(3)>. An application should not call L<SSL_shutdown(3)> on it since
146 you must be careful to not to call any function that uses the connection object
151 A stream object does not inherit all its settings and values from its parent
153 the connection as a whole will not work on a stream. For example the function
163 over QUIC is non-standard and will not be supported by real world servers. This
188 * This is not a requirement for using multiple streams but is recommended.
242 application would not need to do these writes sequentially or in any particular
273 * OpenSSL does not guarantee that the returned data is a string or
380 We should not call L<SSL_shutdown(3)> or L<SSL_shutdown_ex(3)> on the stream
381 objects since those calls should not be used for streams.
397 Licensed under the Apache License 2.0 (the "License"). You may not use