commit | dc1f01133f4bbc21d2c5502c688b1db048c61d84 | [log] [tgz] |
---|---|---|
author | Xin.Zh <dragoncharlie@foxmail.com> | Fri Aug 19 17:27:14 2022 +0800 |
committer | GitHub <noreply@github.com> | Fri Aug 19 17:27:14 2022 +0800 |
tree | 4c82228a7a7bedc4e73ecc0c0b228712bd6a0e7e | |
parent | 69d3bab4c8850403cb40c0938b12340a184c5747 [diff] | |
parent | f0a3eadb2e1e1aa3b102bb5c471b57f5baa9e5c8 [diff] |
Merge pull request #96 from takewofly/fix_benchmark_mb fix: change Aggregate bandwidth
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