| commit | e743d226cac5fb933f22df3517b2b08bc2a6d0ab | [log] [tgz] |
|---|---|---|
| author | watermelon <80680489@qq.com> | Mon Nov 16 00:52:16 2020 +0800 |
| committer | watermelon <80680489@qq.com> | Mon Nov 16 00:52:46 2020 +0800 |
| tree | 209eaf83d289765c8a98906541e9d3da1899ce65 | |
| parent | bf36b5d9404cf0309276ba7c9371c270c98fab52 [diff] |
opt: move taskpool at endpoint layer
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