commit | aabda770021476ef039acd71cd5557a4806514cf | [log] [tgz] |
---|---|---|
author | aliiohs <renzhiyuan@wecash.net> | Wed Aug 12 19:36:58 2020 +0800 |
committer | aliiohs <renzhiyuan@wecash.net> | Wed Aug 12 19:36:58 2020 +0800 |
tree | f6988645d86092e65ec50168a9cd065ba64b8f08 | |
parent | fb33e078217aa2c6604f32d08267592f9ae3426e [diff] |
expose maxWheelTimeSpan
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