Your Conversations applications can display a chat user's online or offline status to other users of the application. This feature is called the Reachability Indicator, and the Conversations service automatically manages the online or offline state for each user if it is activated.
This feature also provides the User's reachability by Push Notification within the Conversations Service instance.
Reachability state is automatically updated and synchronized by the Conversations service, provided the feature is enabled. The feature is enabled on a "per Service instance" basis.
Note: It is important to note that Users exist within the scope of a Conversations Service instance. Thus, the Reachability indicators are also within the same scope.
Each Service instance can have Reachability enabled or disabled. The default is disabled. Reachability state will not be updated if the feature is disabled for a given Service instance. Once enabled, the state will update and synchronize.
You must set the
ReachabilityEnabled property using the
Service Configuration REST resource to configure the Reachability Indicator feature.
If you choose to enable Reachability Indicators and later wish to return to
disabled, set the
ReachabilityEnabled property back to
The Reachability indicators are exposed for Users in two places:
- REST API - Userリソース
- Client SDKs - User objects
The following read-only properties within the Users REST resource provide Reachability information for Users:
These properties are set by the Conversations system if the Reachability Indicator feature is enabled for a User's Service instance.
LIST GETresource representations only have a
falsevalue for specific GET requests
Within the Conversations Client SDKs, the Reachability Indicator properties are exposed in the
Real-time updates to other Users' Reachability Indicator states are communicated via the
update event mechanism for subscribed User objects. Please see the specific SDK API documentation for details, as each SDK/platform handles this
update a little differently.
An indicator of your Service instance's Reachability status (
reachability_enabled ) is also exposed at the SDK client level.
Note: The above are representations. The specifics of how these properties are accessed are distinct for each language/SDK.
Note: These user properties are
read only and cannot be set. Conversations will update these settings and synchronize them as necessary. The Service Configuration REST resource manages the Service-level Reachability feature from the back-end code.