commit | 1936cf8d5ad6d2cafefc581a381a218831550faf | [log] [tgz] |
---|---|---|
author | Xin.Zh <dragoncharlie@foxmail.com> | Mon Jul 31 14:52:14 2023 +0800 |
committer | GitHub <noreply@github.com> | Mon Jul 31 14:52:14 2023 +0800 |
tree | 8ae6be6917cf133ba56722b98b3282dce9d7d7b4 | |
parent | 2ecc34277bc9691f38ca87afc290d5abf64208ef [diff] | |
parent | 1dea1c95f54016b8a3168bae990a05131519f44f [diff] |
Merge pull request #102 from iSuperCoder/feature/sync_from_alexstocks chore: unnecessary use of fmt.Sprintf
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