| commit | 3da63c3257fa5de8e2ca013ae32b0b4702b5dd9c | [log] [tgz] |
|---|---|---|
| author | Xin.Zh <dragoncharlie@foxmail.com> | Thu Aug 25 10:45:08 2022 +0800 |
| committer | GitHub <noreply@github.com> | Thu Aug 25 10:45:08 2022 +0800 |
| tree | ed3381f0dafb0cefe565e01e2c24c78eb531fc27 | |
| parent | dc1f01133f4bbc21d2c5502c688b1db048c61d84 [diff] | |
| parent | 532ea3f6acf214d197055623db6d8690450b679c [diff] |
Merge pull request #97 from Leospard/master Update gost
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