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. ac07194 Merge pull request #124 from No-SilverBullet/master by Xin.Zh · 6 hours ago master
  2. 84504ea Merge pull request #4 from No-SilverBullet/refactor/tcp_reconnect_var_rename by xinfan.wu · 17 hours ago
  3. e64ed0c refact:rename the variable name in TCP reconnect by xinfan.wu(吴歆帆) · 17 hours ago
  4. a96fbf7 Merge pull request #123 from No-SilverBullet/master by Xin.Zh · 12 days ago v1.5.0
  5. 56834ab Merge pull request #3 from No-SilverBullet/fix/ws-read by xinfan.wu · 13 days 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