a netty like asynchronous network I/O library based on tcp/udp/websocket; a bidirectional RPC framework based on JSON/Protobuf; a microservice framework based on zookeeper/etcd

Clone this repo:
  1. 6a6e1d1 Merge pull request #117 from No-SilverBullet/fix/reconnect by Xin.Zh · 14 days ago master v1.4.11
  2. ce6736e Merge pull request #118 from Jardaliao/fix-closing-connection-returns-invalid-code by Xin.Zh · 14 days ago
  3. b33c1e6 fix:maxDuration typo by No-SilverBullet · 3 weeks ago
  4. 05a6a9a style:change the declaration location ofreconnect-related variables by No-SilverBullet · 3 weeks ago
  5. 0c0272c style:format code by No-SilverBullet · 3 weeks ago

getty

a netty like asynchronous network I/O library

Build Status codecov go.dev reference Go Report Card license

INTRO

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.

LICENCE

Apache License 2.0