@fluidframework/datastore-definitions
Advanced tools
Interface IFluidDataStoreRuntime specifies the data store developer API.
IFluidDataStoreRuntimeTODO: The full set of functionality is under review
Signals provide a transient data channel for data (any serializable payload) that doesn't need to be persisted in the op stream. Use signals where possible to avoid storing unnecessary ops, e.g. to transmit presence status during a collaborative session.
Signals are not persisted, ordered, or guaranteed. If a client is behind, the op state can be behind the signal state. For this reason people usually stick the currentSeq on the signal, so other clients can wait to process if they are behind.
You can send a signal via the container or data store runtime. The container will emit the signal event on all signals, but a data store will emit the signal event only on signals emitted on that data store runtime.
FAQs
Fluid data store definitions
We found that @fluidframework/datastore-definitions demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
PyPI confirms no security flaws were exploited in the Ultralytics supply chain attack and highlights improvements for safer package publishing.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.