How aceld/zinx works
Project type and purpose
• This is “Zinx,” a Golang-based, lightweight concurrent TCP-server framework.
• It provides core modules for building long-linked services (games, message routers, etc.), plus hooks for middleware, async operations, logging, timers, and configuration.
File structure
• Top-level “znet” folder: core server components (Server, Connection, ConnManager, Router, MsgHandler, WorkerPool).
• “ziface”: all interfaces (IConnection, IServer, IRequest, IRouter, IDecoder, IDataPack, IInterceptor, IClient, etc.).
• “zpack”: message framing (TLV/LTV packers).
• “zdecoder”: CRC and TLV decoders.
• “zinterceptor”: interceptor chain for pipeline processing.
• “zasync_op”: asynchronous-task engine.
• “znotify”: publish/subscribe notifications.
• “ztimer”: delay/timer scheduler.
• “zconf”: configuration loader.
• “zlog”: pluggable logging core.
• “zutils”: common utilities (UUID, locks, hashing).
• “examples/…” and “zinx_app_demo/…” host sample servers/clients illustrating framework use.
README for architecture
• Describes server startup, connection hooks, router registration, message dispatch, worker pools.
Elements
• Clear labels for each package/component