commit | 0e5e138f2b48e768ce9397b4a964d9ea3262f5fc | [log] [tgz] |
---|---|---|
author | cvictory <shenglicao2@gmail.com> | Fri Jan 29 16:44:03 2021 +0800 |
committer | cvictory <shenglicao2@gmail.com> | Fri Jan 29 16:47:11 2021 +0800 |
tree | 4eec889b2b9707506d8ae105f25edeb47147cc2e | |
parent | e2bdee6b4763d88244f9826922ea75faf5916fe8 [diff] |
review issue
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