commit | 03651cac3cd132282e0c7be2f378703fb886c1a3 | [log] [tgz] |
---|---|---|
author | Xin.Zh <dragoncharlie@foxmail.com> | Thu Jul 01 19:32:43 2021 +0800 |
committer | GitHub <noreply@github.com> | Thu Jul 01 19:32:43 2021 +0800 |
tree | cb5788d3458dd95cd93e88691ebd62e91e55df71 | |
parent | f9499a7eebebf6d58ef41748d2aaf3a52a6ea5f3 [diff] | |
parent | 17b08dc42dd664ddfbe70433226253614619117a [diff] |
Merge pull request #68 from luoyunhe/fix fix conn data race
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