commit | 3c3a31831abca17782e65703a51bbbdb7a3f62b8 | [log] [tgz] |
---|---|---|
author | jason <lvs.pjx@gmail.com> | Sat Oct 30 12:30:14 2021 +0800 |
committer | jason <lvs.pjx@gmail.com> | Sat Oct 30 12:30:14 2021 +0800 |
tree | 6f2772ecea48480a166f6d3ed347e6b5868b3d97 | |
parent | 9c46f0f823a52382c2af06df1cf5de5a587f3c0b [diff] |
fmt for license
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