commit | 193d5d02756b5d18513058d34b413303bdd07863 | [log] [tgz] |
---|---|---|
author | 望哥 <gelnyang@163.com> | Tue Oct 01 23:21:44 2019 +0800 |
committer | GitHub <noreply@github.com> | Tue Oct 01 23:21:44 2019 +0800 |
tree | d0e87b237d4e6416cd8765d1992470b84ed87311 | |
parent | c34c7a71a0e60c900c7855a83db2caa0bd1d6d8a [diff] | |
parent | 085aa6778ed1be3118428decd6c18d1b12a39e9f [diff] |
Merge pull request #30 from dubbo-x/issue29 Fix issue29: skip the log output of EOF error
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