commit | 4965ba8b512b66600c5e518ee089f6cf33c7006b | [log] [tgz] |
---|---|---|
author | Xin.Zh <dragoncharlie@foxmail.com> | Mon Jul 20 00:23:10 2020 +0800 |
committer | GitHub <noreply@github.com> | Mon Jul 20 00:23:10 2020 +0800 |
tree | 8499cc82db7e6317b13b224ffad508a4a79a7467 | |
parent | 58244ae517fea201c7aea578c797bc9f9e2b0be2 [diff] | |
parent | 3c5b952d847cd0569eaf1eb0f3fcdef23e9e8822 [diff] |
Merge pull request #42 from zaihang365/featrue/ReplacePkgs Mod: replace some pkgs
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