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
I wonder if it would be nice to have sequential ID's on events, so that during playback the player can detect if events are missing, out of order, or duplicated (and same within our own app layer).
I recently fixed an issue on our end where sessions weren't replaying due to missing snapshots (ultimately because payloads were failing to reach our server). However, I wonder if other cases would be harder to detect, such as events missing in the middle, or duplicate events, especially as we work on fancier things like long-lived sessions, live streaming sessions, buffering in chunks, etc.
These ID's could also be added ourselves within the app layer, I just wonder if it would have additional usefulness for debugging if it was baked into the library itself, so thought I would start a discussion.
The text was updated successfully, but these errors were encountered:
I wonder if it would be nice to have sequential ID's on events, so that during playback the player can detect if events are missing, out of order, or duplicated (and same within our own app layer).
I recently fixed an issue on our end where sessions weren't replaying due to missing snapshots (ultimately because payloads were failing to reach our server). However, I wonder if other cases would be harder to detect, such as events missing in the middle, or duplicate events, especially as we work on fancier things like long-lived sessions, live streaming sessions, buffering in chunks, etc.
These ID's could also be added ourselves within the app layer, I just wonder if it would have additional usefulness for debugging if it was baked into the library itself, so thought I would start a discussion.
The text was updated successfully, but these errors were encountered: