You seem to be thinking that this is a mere virtual machine idea like a VNC or pcAnywhere solution - but according to the article the application actually takes system calls for saves, etc. and redirects them over the network to the central server - and it says that a network connection is only required when a full save is required - it caches what the user is doing. VNC stays connected all the time and is subject to network speed and overload - something that this type of idea is not.
Our company uses a very interesting naming convention - name it for the OS.
Most of the servers are running NT, so they are named NTxxxx where NT is a progressive name. So you never know if you're copying to the right server or not. Who's to know that nt17 is the mail server? If it's a non-NT box, then it's named SVxxxx in another progressing fashion.
Disclaimer: This was sarcasm. I in no way recommend actually using this type of thing.
Slashdot Mirror
You seem to be thinking that this is a mere virtual machine idea like a VNC or pcAnywhere solution - but according to the article the application actually takes system calls for saves, etc. and redirects them over the network to the central server - and it says that a network connection is only required when a full save is required - it caches what the user is doing. VNC stays connected all the time and is subject to network speed and overload - something that this type of idea is not.
Our company uses a very interesting naming convention - name it for the OS. Most of the servers are running NT, so they are named NTxxxx where NT is a progressive name. So you never know if you're copying to the right server or not. Who's to know that nt17 is the mail server? If it's a non-NT box, then it's named SVxxxx in another progressing fashion. Disclaimer: This was sarcasm. I in no way recommend actually using this type of thing.