commit | ada6920613c7ea053ec9b79afec1f9ebd5ae6276 | [log] [tgz] |
---|---|---|
author | dongjianhui03 <dongjianhui03@meituan.com> | Sat Aug 21 22:37:58 2021 +0800 |
committer | dongjianhui03 <dongjianhui03@meituan.com> | Sat Aug 21 22:41:56 2021 +0800 |
tree | 3957f43aac86cf7f87f3be3012806ca6ee19da18 | |
parent | c8ebbd87375475b1636f157aaa4b07c2df23d76d [diff] |
rft(*): reorganize code with proper file name
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