commit | 4033bd30bf2a49962f396dec8baf7e9fd915ed07 | [log] [tgz] |
---|---|---|
author | hongshengjie <hongshengjie@live.com> | Sat Mar 16 22:10:21 2024 +0800 |
committer | hongshengjie <hongshengjie@live.com> | Sat Mar 16 22:43:54 2024 +0800 |
tree | 91ee525a0a5d3609cce93f9a612b00085993530c | |
parent | 71b8185885e8905e3a0aac98837a7793d3ca9036 [diff] |
bufix: add tlsHandshake timeout to prevent readtimeout cause dead loop
a netty like asynchronous network I/O library
Getty is a asynchronous network I/O library in golang. Getty works on tcp/udp/websocket network protocol and supplies a uniform interface.
In getty there are two goroutines in one connection(session), one reads tcp stream/udp packet/websocket package, the other handles logic process and writes response into network write buffer. If your logic process may take a long time, you should start a new logic process goroutine by yourself in codec.go:(Codec)OnMessage.
You can also handle heartbeat logic in codec.go:(Codec):OnCron. If you use tcp/udp, you should send hearbeat package by yourself, and then invoke session.go:(Session)UpdateActive to update its active time. Please check whether the tcp session has been timeout or not in codec.go:(Codec)OnCron by session.go:(Session)GetActive.
Whatever if you use websocket, you do not need to care about hearbeat request/response because Getty do this task in session.go:(Session)handleLoop by sending/received websocket ping/pong frames. You just need to check whether the websocket session has been timeout or not in codec.go:(Codec)OnCron by session.go:(Session)GetActive.
Apache License 2.0