commit | 1643183fa5dc86d6203e156bf3cffd28550a9c6a | [log] [tgz] |
---|---|---|
author | Xin.Zh <dragoncharlie@foxmail.com> | Sat Mar 16 12:31:38 2024 +0800 |
committer | GitHub <noreply@github.com> | Sat Mar 16 12:31:38 2024 +0800 |
tree | 9cb63806a610b934f2065ae8d6c79ef8cc6c5c94 | |
parent | 04b11652a73c45d731244b2bd45b9ea9313bd236 [diff] | |
parent | 985ac665285437594d72dc820c35042307fb99b2 [diff] |
Merge pull request #112 from DMwangnima/chore/upgrate_go_to_1.20 chore: upgrade go version from 1.14 to 1.20
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