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
Hi, I've been working on persistence for pycrdt recently. In the project, the store(ystore) seems to grow infinitely. Do we need to provide a trim method for update compression?
I noticed that when a new connection is established, the latest document is directly synchronized, instead of transferring all the updates for the client to redo/undo.
Proposed Solution
It seems that we don't need to save all updates, just the most recent ones? Providing a trim method allows the server to compress updates that no longer needed, similar to disk organizing.
Additional context
The text was updated successfully, but these errors were encountered:
Oh thanks! I referenced the FileYStore implementation and missed the SQLiteYStore's. Sorry about that! The document_ttl implementation is basically the same as my thoughts :)
Out of curiosity, does FileYStore doesn't require trim, or is there another way to safely trim them?
Problem
Hi, I've been working on persistence for
pycrdt
recently. In the project, the store(ystore
) seems to grow infinitely. Do we need to provide atrim
method for update compression?I noticed that when a new connection is established, the latest document is directly synchronized, instead of transferring all the updates for the client to redo/undo.
Proposed Solution
It seems that we don't need to save all updates, just the most recent ones? Providing a
trim
method allows the server to compress updates that no longer needed, similar to disk organizing.Additional context
The text was updated successfully, but these errors were encountered: