commit | ceb444b8ebd23d57bfe11f5f33ace8a0f1a106a6 | [log] [tgz] |
---|---|---|
author | Xin.Zh <dragoncharlie@foxmail.com> | Fri Feb 18 15:30:16 2022 +0800 |
committer | GitHub <noreply@github.com> | Fri Feb 18 15:30:16 2022 +0800 |
tree | ff2af2509484d90466c567f577479e741346c76f | |
parent | 0b14a0dc61b146861a2d042eb8a580d6823a820c [diff] | |
parent | 2a4b90960885d5c3c0f785fc4a630d4867c9fdb9 [diff] |
Merge pull request #93 from takewofly/fix/dep Imp: remove goext & log4go in go mod
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