-
-
Notifications
You must be signed in to change notification settings - Fork 116
Description
Firstly, I just want to thank you for this project, it's amazing!
Is your feature request related to a problem? Please describe.
Our setup involves a central server running a WsServer with data persistence. We then have clients that connect over the web with data persisted in the browser via the Pglite persister. For the particular (mergeable) store in question, data is only loaded on the client. Nothing is saved back to the server.
When a client connects to the server and there are currently no other active clients, all of the data in the store is transmitted to that client regardless of what data it already has. When subsequent clients connect, however, only the necessary changes are sent. I assume this is related to the fact that the persister for the WsServer path is stopped when there are no active clients (as mentioned here).
This is problematic for us because we have a considerable amount of data in the store and it would be preferable if it wasn't all sent when it's not required.
Describe the solution you'd like
An option to disable the above behaviour and have only the relevant data sent to a client even if it is the first one to connect to the server.
Describe alternatives you've considered
As a workaround, we are maintaining a connection to the store on the server to ensure that there is always at least one client connected but this is not ideal.