| tag | 1c6e5e21c37092f81ec8ab0356e41d6e7ef0d806 | |
|---|---|---|
| tagger | AlexStocks <alexstocks@foxmail.com> | Sat Jan 11 21:44:08 2020 +0800 |
| object | a57b22edbb3a7de383ad7a94387000bfd4eca194 |
Imp: enlarge time wheel span from 2m to 15m
| commit | a57b22edbb3a7de383ad7a94387000bfd4eca194 | [log] [tgz] |
|---|---|---|
| author | AlexStocks <alexstocks@foxmail.com> | Sat Jan 11 21:36:11 2020 +0800 |
| committer | AlexStocks <alexstocks@foxmail.com> | Sat Jan 11 21:36:11 2020 +0800 |
| tree | 3c8d4f4b1558f5a3fe06d7616bf36bfaa22f301a | |
| parent | 2f6fb0321db222250315fe8d1426d4e4d0e9e194 [diff] |
Imp: enlarge time wheel span from 2m to 15m
a netty like asynchronous network I/O library
Getty is a asynchronous network I/O library in golang. Getty is based on “ngo” whose author is sanbit. 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.
You can get code example in https://github.com/AlexStocks/getty-examples.
Apache License 2.0