On 1/6/2024 12:04 PM, Cao Duc Quan wrote:
"During" means the time since the Server sends the GOAWAY frame till
the Server explicitly closes the TCP connection. This window is 60s.
My library starts a new connection with an HTTP GET to the server and
the server will respond in multipart. This HT
Sorry, seems I only replied to you in previous emails.
Are you saying that you want to proactively drop the in-progress streams as
> soon as a GOAWAY frame has been received?
No, it's not. With the patch I proposed, on the callback of the
GOAWAY frame, I did the following logic:
- 1. Create a new
I think what I proposed for GOAWAY has the same idea as
CURLOPT_PREREQFUNCTION.
What do you think?
On Sun, Jan 7, 2024 at 10:24 AM Cao Duc Quan wrote:
> Sorry, seems I only replied to you in previous emails.
>
> Are you saying that you want to proactively drop the in-progress streams
>> as soon
On 1/7/2024 1:33 PM, Cao Duc Quan wrote:
I think what I proposed for GOAWAY has the same idea as
CURLOPT_PREREQFUNCTION.
What do you think?
On Sun, Jan 7, 2024 at 10:24 AM Cao Duc Quan wrote:
Sorry, seems I only replied to you in previous emails.
Are you saying that you want to p
>
> You are asking for a low level signal that almost nobody needs. It sounds
> like you are trying to work around a server or application issue.
Agree my use case is quite odd but that is the protocol we developed for
years and I saw the benefit of having this low-level signal. Is there any
down-
