commit | ccec1329b08f7c361360c87405a937d4c8e521e3 | [log] [tgz] |
---|---|---|
author | alexstocks <alexstocks@foxmail.com> | Thu Mar 14 17:45:18 2024 +0800 |
committer | alexstocks <alexstocks@foxmail.com> | Thu Mar 14 17:45:18 2024 +0800 |
tree | 082d8ae58842f0edf37adb3eef89045ed3009b03 | |
parent | 7c0f0039e59c4950bcb14c2d1734655bfd0809d8 [diff] |
disable SetReadDeadline/SetWriteDeadline optimization alg because Go has fix the timer-cpu bug
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