Fernan Dolz, Apologies for the delay and the lengthy response; I've compiled insights addressing all your specific questions.
Based on my understanding of your issue description, you are leveraging the sample outlined in this doc: Quickstart: Dice roller
- For the deployment timeout, you may re-try and let us know if you see any specific error.
AzureFunctionTokenProvider is a token provider that does not expose the secret key in client-side code and can be used in production scenarios.
Also review - Incremental summaries uploaded to Azure Fluid Relay must not exceed 28 MB. If the document size surpasses 95 MB, client load or join requests will fail. Operations, which are incremental updates sent via the websocket, are limited to 700 KB each.
2.The Azure Fluid Relay service allows a maximum of 100 users to participate in a single session simultaneously. This means that if a 101st user attempts to join, they will be unable to do so. However, if a current participant leaves the session, a new user can join, as the total number of simultaneous users will then fall below the limit.
3.Based on your requirement, you may leverage Azure calculator to estimate the cost.
https://azure.microsoft.com/pricing/calculator
(It provides for per month, you can extrapolate for 3 months)
- To connect to an Azure Fluid Relay instance, you first need to create an
AzureClient
. You must provide some configuration parameters including the tenant ID, service URL, and a token provider to generate the JSON Web Token (JWT) that will be used to authorize the current user against the service.
References:
- How to: Connect to an Azure Fluid Relay service
- Authentication and authorization in your app
- Azure Fluid Relay limits
If the answer helped (pointed, you in the right direction) > please click Accept Answer to benefit the community find answers quickly to similar question.