buvidk1234 90a222bfec

fix(msggateway): reset read deadline in pong handler to prevent Web client timeout ...

Root cause:
Due to browser API restrictions, Web (Wasm) clients cannot actively send standard WebSocket Ping frames. They rely entirely on server-initiated Pings (every 27s) and automatic browser Pong responses to maintain the connection. The `pongHandler` was empty and failed to reset the connection's read deadline upon receiving a Pong, causing the server's read loop to strictly time out at 30 seconds.

Solution:
Call `c.setReadDeadline()` inside the `pongHandler` to properly extend the connection's lifespan when a Pong frame is received.

2026-05-04 02:17:31 +08:00

..

api

merge: pre-release-v3.8.4 (#3623)

2025-11-25 08:23:22 +00:00

msggateway

fix(msggateway): reset read deadline in pong handler to prevent Web client timeout

2026-05-04 02:17:31 +08:00

msgtransfer

feat: implement DeleteConversations interface. (#3549)

2025-11-05 06:16:23 +00:00

push

fix: performance issues with Kafka caused by encapsulating the MQ interface (#3485)

2025-07-28 09:10:38 +00:00

rpc

bugfix(conversation):removed unexpectedly called functions and itself to avoid out of index query. (#3668)

2026-01-21 10:10:29 +00:00

tools/cron

fix: update log level in crontask dist look. (#3440)

2025-07-08 08:33:25 +00:00