Chrome RDP

[this user was banned]

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

Chrome RDP doesn't work like other incantations of RDP. It runs virtual applications, cloned from RAM of the viewed PC, locally on the viewer machine and superimposes them over cropped jpgs or png or whatever sent from the viewed PC. That way the images transferred can be much smaller, and bandwidth constraints are much less an issue. It's a wild implementation. Side effects, of course, Google gets to read the state of the applications and track user behavior thoroughly for advertising. And the traffic can be read by IP log and deep package inspection as though the remote machine were local. Check out the docs, chrome rdp is wackadoodle af.

Ok, but isn't the only socket connection to EQ being run on the home PC's hardware? You can't trace that from RDP if the physical machine has no connection to his work PC other than through the HTTPs based RDP connection.

Or does Chrome use your local PC's hardware for networking instead of the home PC?

If you started EQ on the home PC then connected to it and picked it up at work, the process and socket are only running on the home PC, otherwise EQ will just not work because it would need to open a new connection on new hardware. Maybe there's something I'm missing?