commit | 5b7d8d26ed7ce36d666098258bcfc15118868dba | [log] [tgz] |
---|---|---|
author | Xin.Zh <dragoncharlie@foxmail.com> | Tue Jul 27 22:41:34 2021 +0800 |
committer | GitHub <noreply@github.com> | Tue Jul 27 22:41:34 2021 +0800 |
tree | cb8eb4b7482d8496a70e7a3396008e16224d5481 | |
parent | 168f412b5df6b4e452212626b41c15d613d6af47 [diff] | |
parent | 3ea0e197e559b6c806dd123b1ff94b193188569f [diff] |
Merge pull request #69 from Mulavar/imports-fmt style(*): format all imports with dubbogo/tools/imports-formatter
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