You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Release Notes
Added shared event loop support for client networking operations.
Added new EzyTcpClient(EzyClientConfig, EzyEventLoopGroup) and EzyUTClient(EzyClientConfig, EzyEventLoopGroup) usage paths so TCP, UDP/TCP clients, socket adapters, and ping schedules can run on a provided EzyEventLoopGroup.
startProcessEvents(EzyEventLoopGroup eventLoopGroup, int sleepTime)
stopProcessEvents()
EzyClients can now process events for all registered clients automatically, either through an owned event loop, a provided event loop group, or a scheduled executor.
Clients created through EzyClients.newClient now reuse the shared process-events event loop group when one has been started.
Socket connection and reconnection tasks can now be scheduled through EzyEventLoopGroup instead of always creating dedicated connection threads.
Added process-events constants: PROCESS_EVENTS_PERIOD and ONE_THREAD.
Changed EzyClients.removeClient to return the removed EzyClient, and EzyClients.clear to return the removed client map.
Improved tests for shared event loop behavior across TCP, UDP/TCP, ping scheduling, reconnect flow, and EzyClients process-events lifecycle.
Performed minor internal cleanups around logging, queue checks, Lombok-generated setters/getters, and file formatting.