commit | 66f2506123c17f6d04fd643c1a6fef06e773af37 | [log] [tgz] |
---|---|---|
author | Xin.Zh <dragoncharlie@foxmail.com> | Thu Oct 28 10:18:08 2021 +0800 |
committer | GitHub <noreply@github.com> | Thu Oct 28 10:18:08 2021 +0800 |
tree | 07248209d9041df1e6f40b8200b2e36f70eb93a0 | |
parent | d58f9f3522abb67628e49b300026dec50e87dbfc [diff] | |
parent | 04c5bef7cb67750355800f683727561934c0261e [diff] |
Merge pull request #80 from takewofly/bug/race Opt: change timeout to atomic
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