smart-socket v1.8.0: Streamlined Core, IdleStatePlugin Timeout Revamp, and API Simplifications

smart-socket v1.8.0 trims unused plugins, refines the IdleStatePlugin timeout logic to require simultaneous read‑write idle before closing, and simplifies the API by renaming session types and deprecating methods, all to deliver a leaner, more stable high‑performance AIO networking framework.

Three Knives
Three Knives
Three Knives
smart-socket v1.8.0: Streamlined Core, IdleStatePlugin Timeout Revamp, and API Simplifications

smart-socket v1.8.0 core changes

Removed rarely used plugins

BlackListPlugin

: blacklist handling HeartPlugin: heartbeat management ReconnectPlugin: reconnection logic SocketOptionPlugin: socket option configuration StringProtocol: string‑based protocol support

Migration note: copy the plugin source from the previous version if needed; the framework core remains unchanged.

IdleStatePlugin timeout strategy improvement

Testing with Feat Agent in SSE scenarios showed that long idle write periods caused unexpected connection closures and incomplete reads.

Before: a timeout in either read or write triggered connection closure.

Now: the connection closes only when both read and write operations satisfy the timeout simultaneously.

This change prevents disconnections caused by one‑sided idle periods, improving stability and data completeness.

API adjustments and deprecations

The return type of AioQuickClient@getSession changed from TcpAioSession to AioSession.

The method AioSession@getSessionID is deprecated.

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

backendPerformancenetworkingAPI changesAIOplugin removalsmart-socketIdleStatePlugin
Three Knives
Written by

Three Knives

Every line of code you contribute to open source could help make the future better.

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.