Missing Unsubscribe Methods for WebSocket Streams in JSON-RPC

[blouflashdb]

Missing Unsubscribe Methods for WebSocket Streams in JSON-RPC

The current implementation of the JSON-RPC offers the ability to subscribe to WebSocket streams, which is a great feature. However, there appears to be a critical issue: there is no corresponding unsubscribe method available to gracefully close these streams.

This absence creates challenges in managing resources effectively, especially in scenarios where multiple subscriptions are created dynamically. Without a proper unsubscribe method, it becomes difficult to cleanly terminate streams, leading to potential memory leaks and unnecessary resource consumption on both the client and server sides.

To address this, I suggest adding an unsubscribe method for each available subscription type. This would allow developers to properly close WebSocket streams when they are no longer needed, ensuring a cleaner and more efficient implementation.

Let me know if further details are needed, or if you'd like help testing any changes!