A simple and powerful way to consume collaborative Fluid data with the Azure Fluid Relay.
|AzureClient||AzureClient provides the ability to have a Fluid object backed by the Azure Fluid Relay or, when running with local tenantId, have it be backed by a local Azure Fluid Relay instance.|
|AzureFunctionTokenProvider||Token Provider implementation for connecting to an Azure Function endpoint for Azure Fluid Relay token resolution.|
|AzureClientProps||Props for initializing a new AzureClient instance|
|AzureConnectionConfig||Parameters for establishing a connection with the Azure Fluid Relay.|
|AzureContainerServices||AzureContainerServices is returned by the AzureClient alongside a FluidContainer. It holds the functionality specifically tied to the Azure Fluid Relay, and how the data stored in the FluidContainer is persisted in the backend and consumed by users. Any functionality regarding how the data is handled within the FluidContainer itself, i.e. which data objects or DDSes to use, will not be included here but rather on the FluidContainer class itself.|
|AzureMember||Since Azure provides user names for all of its members, we extend the IMember interface to include this service-specific value. It will be returned for all audience members connected to Azure.|
|ITokenProvider||The ITokenProvider abstracts the token fetching mechanism for a host. Host will be responsible for implementing the interfaces.|
|IUser||Base user definition. It is valid to extend this interface when adding new details to the user object.|
|LOCAL_MODE_TENANT_ID||Strongly typed id for connecting to a local Azure Fluid Relay.|
|IAzureAudience||Audience object for Azure Fluid Relay containers|
export declare enum ScopeType
Strongly typed id for connecting to a local Azure Fluid Relay.
LOCAL_MODE_TENANT_ID = "local"
Audience object for Azure Fluid Relay containers
export declare type IAzureAudience = IServiceAudience<AzureMember>;