> Thanks for your reply,.Yes, I don't do repeated request. Maybe come
> a request, then next one come an hour later. But the requests are latency
> concered(should be less than 50ms) . If every request comes, then
> make a new connection to the server, the total cost of the request would
> prob
What I was doing is to send keepalive requests to the server. I'm just
wondering if there is a more graceful solution.
Anyway, thanks for your solution.
--
Best wishes!
At 2022-01-21 02:10:46, "Max Dymond" wrote:
>> Thanks for your reply,.Yes, I don't do repeated request. Maybe
On Sun, 23 Jan 2022, 白水月 wrote:
What I was doing is to send keepalive requests to the server. I'm just
wondering if there is a more graceful solution.
TCP keepalive is rarely enough to maintain a connection. It usually also
requires actual TCP traffic to go over it, which in the HTTP/2 case c
On 23-Jan-22 05:46, Daniel Stenberg via curl-library wrote:
On Sun, 23 Jan 2022, 白水月 wrote:
What I was doing is to send keepalive requests to the server. I'm
just wondering if there is a more graceful solution.
TCP keepalive is rarely enough to maintain a connection. It usually
also require
Thanks for your constructive reply. Yet I do send a keepalive request to the
server. It works something just like an "echo".
--
Best wishes!
在 2022-01-23 18:46:14，"Daniel Stenberg" 写道：
>On Sun, 23 Jan 2022, 白水月 wrote:
>
>> What I was doing is to send keepalive requests to the server. I
