commit | ff08429119ba3b4d1e6bbbb4166a9cdd85478b47 | [log] [tgz] |
---|---|---|
author | Xin.Zh <dragoncharlie@foxmail.com> | Wed Dec 02 20:08:52 2020 +0800 |
committer | GitHub <noreply@github.com> | Wed Dec 02 20:08:52 2020 +0800 |
tree | 203972683c19adfc707b4a58b10a0ea5802796f9 | |
parent | 2827ac576ae54ed1b14aee242e5e8b4d2d78156e [diff] | |
parent | ee770be01da9e31e96d313af996cb2cc2858510e [diff] |
Merge pull request #53 from apache/1.4 Rem: session.SetRQLen
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