| commit | 957f65f68d2705f2e1d49e0b0ba318b615fb2597 | [log] [tgz] |
|---|---|---|
| author | watermelon <80680489@qq.com> | Thu Aug 13 15:49:03 2020 +0800 |
| committer | GitHub <noreply@github.com> | Thu Aug 13 15:49:03 2020 +0800 |
| tree | c25af02f24d1abce7bcc2b1c6d68fa9b89b3b98e | |
| parent | fb33e078217aa2c6604f32d08267592f9ae3426e [diff] | |
| parent | f9c6e8b9ad09e10c8f2b07c43a97cb715e88f9ae [diff] |
Merge pull request #46 from aliiohs/exposeMaxWheelTimeSpan Fix:ExposeMaxWheelTimeSpan
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