commit | 84c3a0720f450da8dc1c5e1dafae02a5f5abb80a | [log] [tgz] |
---|---|---|
author | Xin.Zh <dragoncharlie@foxmail.com> | Sat Oct 31 14:41:57 2020 +0800 |
committer | GitHub <noreply@github.com> | Sat Oct 31 14:41:57 2020 +0800 |
tree | 84e2f11dd15f4a5288a16ffe076799b1738e3809 | |
parent | fc4127d58c486844d448b51262caab3b9ac0663d [diff] | |
parent | 353bb67c3183f6a21b8b6f8e37db345b227274a2 [diff] |
Merge pull request #47 from sdttttt/sdttttt-patch-1 Ftr: Migrate travis Ci to GithubActions
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