commit | 76136d06101ba71ffa5f1bc23767eadc3c21f8a2 | [log] [tgz] |
---|---|---|
author | Xin.Zh <dragoncharlie@foxmail.com> | Mon Dec 20 18:58:12 2021 +0800 |
committer | GitHub <noreply@github.com> | Mon Dec 20 18:58:12 2021 +0800 |
tree | fae7573b7440409e838606b1c45cd3a2d2811851 | |
parent | 66e083f7fa3b9c6cd1cbe7624e15a23fca4bcc55 [diff] | |
parent | de68c227d874eb4f8355256263d0d4770f8cb856 [diff] |
Merge pull request #86 from takewofly/feature/log Ipm: change from log4go to dubbo getty default log lib
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