You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In some cases, callers interacting with our APIs directly (for example, users of StreamAllMessages) may need the message ID independent of our SDKs. While it can be computed from values in the envelope, this adds complexity and room for error.
Describe the solution to the problem
We should just include the ID on all envelopes returned from the APIs (Query, Subscribe, Subscribe2, SubscribeAll)
Describe the uses cases for the feature
No response
Additional details
Once completed we will need to update our SDKs to make use of this data and skip client-side generation of IDs
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?
In some cases, callers interacting with our APIs directly (for example, users of StreamAllMessages) may need the message ID independent of our SDKs. While it can be computed from values in the envelope, this adds complexity and room for error.
Describe the solution to the problem
We should just include the ID on all envelopes returned from the APIs (
Query
,Subscribe
,Subscribe2
,SubscribeAll
)Describe the uses cases for the feature
No response
Additional details
Once completed we will need to update our SDKs to make use of this data and skip client-side generation of IDs
The text was updated successfully, but these errors were encountered: