commit | ce6736e6c04f2310c0c25f8fbc3df0e5c15bc85f | [log] [tgz] |
---|---|---|
author | Xin.Zh <dragoncharlie@foxmail.com> | Thu Apr 25 20:02:16 2024 +0800 |
committer | GitHub <noreply@github.com> | Thu Apr 25 20:02:16 2024 +0800 |
tree | 12caa81b80e1a611439d76c962e797d29611adb5 | |
parent | a5233eda4f9a075a965bf285dc2b0dba18bdc440 [diff] | |
parent | 4d3610607415aa97e5afdb5a6d3fb507d225a944 [diff] |
Merge pull request #118 from Jardaliao/fix-closing-connection-returns-invalid-code fix: closing websocket connection returns invalid status code
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