{"author":"Neil Horman","author_email":"nhorman@openssl.org","author_time":1735917476,"commit_time":1736376769,"committer":"Daniel Stenberg","committer_email":"daniel@haxx.se","hash":"957eb240ed7115f89a60c55f441a52ec7886327c","message":"osslq: use SSL_poll to determine writeability of QUIC streams\n\nThis discussion:\nhttps://github.com/openssl/openssl/discussions/23339#discussion-6094341\n\nSpecifically item number 2 (Send Blocking) was raised by the curl team,\nnoting that SSL_want_write returning false was not a good indicator of\nwhen a stream is writeable. The suggestion in that discussion was to use\nSSL_poll with an SSL_POLL_EVENT_W flag instead, as that is a proper\nindication of when an SSL_object will allow writing without blocking.\n\nWhile ssl_want_write updates its state based on the last error\nencountered (implying a need to retry an operation to update the\nlast_error state again), SSL_poll checks stream buffer status during the\ncall, giving it more up to date information on request. This is the\nmethod used by our guide demos (quic-hq-interop specifically), and it\nworks well.\n\nThis change has been run through the curl test suite, and shown to pass\nall tests. However, given the initial problem description I'm not sure\nif there is a test case that explicitly checks for blocking and\nunblocking of streams. As such some additional testing may be warranted.\n\nCloses #15909\n","parents":["616b66e68f8e29db22896da8974a42496affaf4b"],"tree_hash":"857b378b588c55d65274177c24746fe12cffba04"}