commit | 292995d84c7b62fd510c2f64cd54d9e5e00ff290 | [log] [tgz] |
---|---|---|
author | Xin.Zh <dragoncharlie@foxmail.com> | Wed Jan 12 12:54:54 2022 +0800 |
committer | GitHub <noreply@github.com> | Wed Jan 12 12:54:54 2022 +0800 |
tree | 476c64019b1bc1c2fae79e59089aece2244e4f37 | |
parent | 76136d06101ba71ffa5f1bc23767eadc3c21f8a2 [diff] | |
parent | d25d2a84625a364f5eb046f1de3497b553d9fd22 [diff] |
Merge pull request #91 from takewofly/bug/panic Fix: taskPool will execute task when session was nil
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