tag | e771916b2a7c8cc748458d974060e40abfa44f49 | |
---|---|---|
tagger | AlexStocks <alexstocks@foxmail.com> | Mon Apr 27 10:27:53 2020 +0800 |
object | 4f0a9de6bcfbabb382a14cfa5f3ab07233e52873 |
Add: StreamServer & PacketServer
commit | 4f0a9de6bcfbabb382a14cfa5f3ab07233e52873 | [log] [tgz] |
---|---|---|
author | Xin.Zh <dragoncharlie@foxmail.com> | Mon Apr 27 10:23:01 2020 +0800 |
committer | GitHub <noreply@github.com> | Mon Apr 27 10:23:01 2020 +0800 |
tree | 86213fcb48189ea005678f0039160f6f63fe8468 | |
parent | 076a8069a286f2ccc8bd181627a9bcae06453296 [diff] | |
parent | 5cc2deb9c3568ec2c5ce6c91f029644a891b1ba1 [diff] |
Merge pull request #38 from divebomb/master Add: StreamServer & PacketServer
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