passing the flag B<SSL_ACCEPT_STREAM_NO_BLOCK> in I<flags>. If this flag is set,
this function never blocks.
+Calling SSL_accept_stream() if there is no default stream already present
+inhibits the future creation of a default stream. See L<openssl-quic(7)>.
+
SSL_get_accept_stream_queue_len() returns the number of incoming streams
currently waiting in the accept queue.
streams. To accept incoming streams initiated by a peer, use
L<SSL_accept_stream(3)>.
+Calling SSL_new_stream() if there is no default stream already present
+inhibits the future creation of a default stream. See L<openssl-quic(7)>.
+
=head1 RETURN VALUES
SSL_new_stream() returns a new stream object, or NULL on error.
using additional streams are strongly recommended to use multi-stream mode
instead.
+Calling L<SSL_new_stream(3)> or L<SSL_accept_stream(3)> before a default stream
+has been associated with the QUIC connection SSL object will inhibit future
+creation of a default stream.
+
=head2 Multi-Stream Mode
The recommended usage mode for new applications adopting QUIC is multi-stream
is not relevant if the default stream has been disabed as described in
L</THE DEFAULT STREAM> above.
-=begin comment
-
-TODO(QUIC): What happens if SSL_accept_stream()/SSL_new_stream() is called and
-there is no default stream yet? incoming stream policy suggests that all
-incoming streams are rejected by default....but this only applies after a
-default stream has been created?
-
-=end comment
-
Any stream may be bi-directional or uni-directional. If it is uni-directional
then the initiator can write to it but not read from it, and vice-versa for the
peer. You can determine what type of stream an B<SSL> object represents by