Dear All, Thank you for all your feedback. It is informative and appreciated.
Scenarios that I envisioned (not limited to) that I would need to rethink: - Scenario 1: User A creates connection C to a remote resource. User B joins after some time. User A handovers some work and disconnects. User B continues for an unspecified amount of time. User A would like his recording before user B finishes, as its not known when that happens. - Scenario 2: User A creates connection C to a remote resource. He uses it for an unspecified amount of time. User B joins in the middle to be presented with something. User B disconnects shortly after. User B would like to have his recording, while user A still is connected for an unknown foreseen amount of time. I understand that for many cases, separate recordings would be a simple copy and resource waste. I will think of other possibilities for my implementation, and get back here if having more questions. Thank you again, have a great day! On Mon, Jan 12, 2026 at 7:42 AM Palaash Jain <[email protected]> wrote: > Maybe the OP is trying to do something like, > > User A creates Connection A > User B joins Connection A > > Since the output is mirrored, i.e., what User B does is visible to A and > vice versa, > the recording file must contain which user did that particular action - > did User A move the mouse or User B? > > - Palaash >
