Chrome RDP

[this user was banned]

Originally Posted by America [You must be logged in to view images. Log in or Register.]

The EQ instance is cloned from host (or whatever, the viewed machine I mean) to client (viewer) and run locally. Then a bitwise two-way synchronization is done as the application state changes.

It's bizarre. That's why it takes so long to "buffer", though, and why achievable framerate is so high. Check the docs out, it's wild.

Ok, but the ACTUAL TCP connection to EQ is only run through the hardware on the home PC; I'm not sure that network traffic between the home PC and the EQ servers would ever be visible through Chrome RDP.

The network traffic for EQ wouldn't even route through his work PC would it? His work would only be able to monitor his work PC's traffic and they would only see the HTTPS traffic from Chrome RDP.