Quote:
Originally Posted by branamil
[You must be logged in to view images. Log in or Register.]
How about you copy and paste the part from the documentation where it "clones ram"?
|
You're the one giving reckless advice. Maybe the onus is on you.
Quote:
Originally Posted by this user was banned
[You must be logged in to view images. Log in or Register.]
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?
|
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.