commit | 8af010f3f3dc15ba8fec161ce9afbcc31ef1226c | [log] [tgz] |
---|---|---|
author | LaurenceLiZhixin <382673304@qq.com> | Fri Jun 10 14:01:50 2022 +0800 |
committer | LaurenceLiZhixin <382673304@qq.com> | Fri Jun 10 14:01:50 2022 +0800 |
tree | af14ca2196f20814272ca43be6486bfe99dfefbf | |
parent | 1bfc340ef6dc93e78c15b04f3df5d4b815408921 [diff] |
Fix: add recover logic, fix dead loop
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