commit | 9be0aeebaacc081fd5786d27a7de3511c86622f5 | [log] [tgz] |
---|---|---|
author | jason <lvs.pjx@gmail.com> | Fri Oct 22 23:08:11 2021 +0800 |
committer | jason <lvs.pjx@gmail.com> | Sat Oct 23 22:11:53 2021 +0800 |
tree | 38cf9e9a04aacdc50a83af6c5406b109023b2038 | |
parent | 1f01b7111782f1bc62ddef93ad1231d423d752f2 [diff] |
fix license
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