This repository was archived by the owner on Apr 10, 2025. It is now read-only.

Description
It looks like SSL_process_quic_post_handshake only processes a single session ticket in a single call as demonstrated in a test code.
On the other hand, BoringSSL counterpart processes multiple session tickets in a single call.
We might be able to call SSL_process_quic_post_handshake multiple times, but there is an issue: we do not know how many times we should call it. This is because it returns 1 when no data to read is left.
I think it would be very useful if SSL_process_quic_post_handshake can process multiple session tickets just like BoringSSL.