commit | ee770be01da9e31e96d313af996cb2cc2858510e | [log] [tgz] |
---|---|---|
author | AlexStocks <alexstocks@foxmail.com> | Wed Dec 02 20:06:58 2020 +0800 |
committer | AlexStocks <alexstocks@foxmail.com> | Wed Dec 02 20:06:58 2020 +0800 |
tree | ef53a9415be801fcd3231a520f4e8485eade3a12 | |
parent | 8296ef87a7d5241418381763b32fb1e1f89928f8 [diff] |
upgrade 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