commit | 2769505749f6cac370cad36ebcf94e790edabd09 | [log] [tgz] |
---|---|---|
author | Xin.Zh <dragoncharlie@foxmail.com> | Tue May 28 21:15:37 2024 +0800 |
committer | GitHub <noreply@github.com> | Tue May 28 21:15:37 2024 +0800 |
tree | d49415a9be820f4e5c1e533292cef92266a572bf | |
parent | 6a6e1d13bf1f5bea59d43fb0c56194d55b8fd5a5 [diff] | |
parent | 01362ffdf587975bc45d488a21af3f732204e922 [diff] |
Merge pull request #121 from No-SilverBullet/master fix issue120 and issue103: add mutex to prevent data race in websocket write message and use named return values for WritePkg method
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