commit | 0df9283b7576f5f8847515f88b9eb7b99e2fc8cf | [log] [tgz] |
---|---|---|
author | georgehao <haohongfan@gmail.com> | Wed Mar 31 22:28:36 2021 +0800 |
committer | georgehao <haohongfan@gmail.com> | Wed Mar 31 22:28:36 2021 +0800 |
tree | 5c5af76c970306fe710fca89fa71edeabfcc2158 | |
parent | 30e62643dc9d44c3f10b7083ef000e5155e7f710 [diff] |
feat: format use gofumpt
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