tag | ae1b728f9d9da8acde12a4d0a9ac9d782d710c4a | |
---|---|---|
tagger | AlexStocks <alexstocks@foxmail.com> | Mon Dec 14 00:41:37 2020 +0800 |
object | 1bcef0bc35359e7afb7cb91468a8ac1ea13fa7cb |
remove session.wQ
commit | 1bcef0bc35359e7afb7cb91468a8ac1ea13fa7cb | [log] [tgz] |
---|---|---|
author | AlexStocks <alexstocks@foxmail.com> | Mon Dec 14 00:39:42 2020 +0800 |
committer | AlexStocks <alexstocks@foxmail.com> | Mon Dec 14 00:39:42 2020 +0800 |
tree | 53bc7e56694dd3494dc6b6621a043b4066277c74 | |
parent | a68aa365ef3e73613d8a7b47b3b16fbc55f0d5e4 [diff] |
update gost version
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