Skip to content

usage.md

Latest commit

 

History

History
43 lines (29 loc) · 1.72 KB

usage.md

File metadata and controls

43 lines (29 loc) · 1.72 KB
Raw

Usage

简体中文 | Docs Index

Requirements

  • Go 1.25 or newer, matching the module go directive.
  • A Gnalloy application, recipe, example, or benchmark harness that owns lifecycle and deployment configuration.
  • Standalone module verification should set GOWORK=off so the module is tested through its published dependency graph.

Install

go get gnalloy.org/handler-timeout@dev

Import

import "gnalloy.org/handler-timeout"

Integration Pattern

  • Handler constructors usually carry the policy: limits, timeouts, match rules, logging level, recorder, or traffic budget.
  • Handler order matters. Place protocol decoders before handlers that inspect protocol objects, and place outbound encoders after handlers that write protocol objects.
  • Handlers must keep backpressure and message ownership explicit; never retain ByteBuf values without clear lifetime control.

API Selection

Use the API inventory to choose the exact constructor or option type for your protocol path:

go doc gnalloy.org/handler-timeout

Common current entry points:

  • var ErrReadTimeout = errors.New("gnalloy/handler/timeout: read timeout") ...

Cross-Module Assembly

When multiple Gnalloy repositories are developed together, create a local go.work file in your chosen workspace. Keep application-local replace directives out of published library modules unless the change is intentionally temporary and never committed.

Error Handling

Network input, peer behavior, platform capability, and timeout failures must be handled as normal errors. Do not recover protocol correctness by panicking. Return or propagate the module error and close the affected Channel when ownership requires it.