RGB-WG / RFC

Requests for comments RGB change proposals
5 stars 2 forks source link

RCP-240725A: Optional In-Memory Container Persistence Feature #9

Open will-bitlight opened 1 month ago

will-bitlight commented 1 month ago

Background

In rgb-std, we provide memory-based state storage containers such as MemStash and Mem*. We have also implemented a feature named fs for these containers to provide persistent storage. In rgb-std, this feature is optional and not enabled by default. However, in rgb (rgb-runtime), we have enabled the fs feature by default at the workspace level. This requires downstream users, when using rgb, to handle the related API and configure persistent paths even if they do not need persistence.

Proposal

We propose to change this behavior so that persistence for memory containers is also optional when using rgb. The specific changes are as follows:

To ensure consistency of the fs feature, we will also synchronize the configuration changes in the following repositories:

Through these changes, we hope to provide downstream users with more flexibility, allowing them to choose whether to enable persistence features based on their needs.

dr-orlovsky commented 1 month ago

I do agree with the proposal. Can you please work on the implementation?

will-bitlight commented 1 month ago

I do agree with the proposal. Can you please work on the implementation?

No problem, I will implement our proposal in the above Repo :)