Mode Refresh Work: Viewerframe

To truly optimize the "viewerframe mode refresh work," you must understand the pipeline. Let’s walk through a single cycle.

| Type | Blocking | Latency | Use case | |------|----------|---------|----------| | Sync | Yes (UI thread waits) | Low but risky | Debugging, legacy apps | | Async | No (callback/event) | Variable | Production remote desktop | viewerframe mode refresh work

The ViewerFrame is the decoded, rendered frame at the client side. Its operational mode defines: To truly optimize the "viewerframe mode refresh work,"

When saving/loading a session, the current frame mode is lost; it defaults to manual mode on restore. The viewer then shows frame 0 instead of the saved frame.
Severity: Medium (user expectation mismatch) Its operational mode defines: When saving/loading a session,

If client decode falls behind, newer frames may be dropped. The ViewerFrame mode should implement frame age tracking and skip intermediate frames when refresh_interval < decode_time.