Struct DataConfig 

pub struct DataConfig {
    pub enabled: bool,
    pub storage: Option<Arc<dyn ProtocolStateStorage>>,
}

Configuration for the replicated-document data layer.

Self::enabled governs the whole layer: with it off no documents are opened, nothing is persisted, and no capability is advertised to peers.

Fields

enabled: bool

Whether the data layer accepts work at all.

Defaults to true. It defaulted to false while the layer could store documents but not replicate them: advertising a capability with no sync behind it invites peers to expect a sync that never comes. Both halves land in the same release, so no application ever ran against the old default, and the switch is on.

What being on costs an application that ignores documents entirely: nothing at rest and nothing on the wire. The layer allocates when a store is opened, and a capability is advertised in a key package that is sent anyway. What it buys is that an application that does open a store gets replication without discovering a flag.

storage: Option<Arc<dyn ProtocolStateStorage>>

Where documents are stored, when the application wants them somewhere other than the store protocol state already uses.

None — the default — means documents live in the same backend as the rest of protocol state, which is what makes the layer work with zero storage setup: every binding already ships a default provider.

Setting it points documents at SQLite, RocksDB, files, a corporate store, or anything else implementing the same trait, while protocol secrets stay exactly where they are. The two concerns swap independently and the swap is a runtime choice: no rebuild, no cargo feature, and no change to any data API. Anything that makes this harder than assigning this field is a design regression.

Sealing sits above this seam. An adapter is handed sealed bytes and never sees document content, so a custom backend cannot weaken the at-rest posture even by accident.

Logout

wipePersistedState clears the account directory of the default provider. A custom backend is somewhere the bindings cannot know about, so an application that sets this must call the data layer’s own wipe on logout, or documents outlive the account that made them.

Trait Implementations

impl Clone for DataConfig

fn clone(&self) -> Self

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for DataConfig

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Default for DataConfig

fn default() -> Self

Returns the “default value” for a type.

impl<'de> Deserialize<'de> for DataConfig

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl Serialize for DataConfig

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.