@fluidframework/datastore
Advanced tools
A Fluid handle is a handle to a Fluid object like a DataStore or a SharedObject (DDS). It can be used to represent the object in the system and has the capability to get the underlying object by calling get() on it.
The two major interfaces required to implement a Fluid handle are IFluidHandle and IFluidHandleContext defined in fluidHandle.ts.
IFluidHandle has only one method get that is used to retrieve the underlying object it represents. It also extends IFluidHandleContext.
IFluidHandleContext describes a routing context (another IFluidHandleContext) that has a path to this IFluidHandleContext. When creating a Data Store Handle the route context should be the FluidDataStoreRuntime which knows how to reach the FluidDataStore. Similarly, the FluidDataStoreRuntime's route context should be the ContainerRuntime which knows how to reach it.
For more details on Fluid Handles, check this doc.
FAQs
Fluid data store implementation
The npm package @fluidframework/datastore receives a total of 5,116 weekly downloads. As such, @fluidframework/datastore popularity was classified as popular.
We found that @fluidframework/datastore 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
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.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.
