👩💻 Support for non-persisted communication (Ie. Signals) #12345
skylerjokiel
started this conversation in
Azure Features & Functionality
Replies: 1 comment 1 reply
-
|
I'm also considering this scenario, and if this type of session metadata (low latency, no persistence) should be part of the DDS or not. I'm leaning towards it being a separate service since these signals have a different nature. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
For example, using Azure PubSub alongside with Fluid Relay. |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Problem
Currently the only data structures available to developers are persisted ones (Eg. SharedMap/SharedString). Signals are a way for developers to communicate with other connected clients within the session without incurring the cost of storage associated with persisted data structures.
Goal
Developers using AzureClient and Azure Fluid Relay can leverage non-persisted communication.
Use Cases
The primary scenario is inner session communication of metadata. (Eg. user presence)
Beta Was this translation helpful? Give feedback.
All reactions