commit | 7df84f8ec9e869341f7f968f6a0c73b668d9fbe1 | [log] [tgz] |
---|---|---|
author | watermelo <80680489@qq.com> | Tue Apr 07 15:31:30 2020 +0800 |
committer | watermelo <80680489@qq.com> | Tue Apr 07 15:31:30 2020 +0800 |
tree | 05069eb702ec458d9a229c27cc7ab3460de25ec0 | |
parent | 8b02420a4bc8f7928b22ccf6fb1caaecab5b2e8e [diff] |
Mod: writePkgNum count
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