commit | 06db3ffe3365af1c5b4fffced1bf560d9244461e | [log] [tgz] |
---|---|---|
author | jason <lvs.pjx@gmail.com> | Mon Nov 22 23:25:46 2021 +0800 |
committer | jason <lvs.pjx@gmail.com> | Mon Nov 22 23:41:10 2021 +0800 |
tree | f88eb037084c111f1ca2dbe15369dd7d7671f462 | |
parent | 16374d23ddab3f4878915f5860719b2a03dd08a0 [diff] |
Ftr: move getty's example to dubbo-getty
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