commit | 1f33b205a929aa0324ab97875c602abbf603bbc3 | [log] [tgz] |
---|---|---|
author | Xin.Zh <dragoncharlie@foxmail.com> | Wed Aug 11 19:02:32 2021 +0800 |
committer | GitHub <noreply@github.com> | Wed Aug 11 19:02:32 2021 +0800 |
tree | f00acbc56738e79228571d2c3957e79940b7419a | |
parent | 5b7d8d26ed7ce36d666098258bcfc15118868dba [diff] | |
parent | d711a4ba565e6b36b0171b3a7e19e22a3550254c [diff] |
Merge pull request #72 from Mulavar/fix/timeout fix(*): revert 17b08d to fix timeout error
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