Linked by Thom Holwerda on Mon 30th Nov 2009 23:45 UTC
Permalink for comment 397379
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
More News »
Sponsored Links



Member since:
2006-02-05
I agree. VNC was originally conceived to do this -- keep a user's session (and data) open on a server while the user roamed from room to room, PC to PC. It works great in a local/LAN environment, though maybe wastes some local PC power if the PCs are full-blown desktops.
The big drawback is the requirement for full-time network connectivity, which might be an issue while traveling and such. But I can live with having to copy my files in that case. Migrating several GB worth of OS, data and session every time I switch machines seems rather inefficient.
I want to set something up like this at home as well. I haven't seen VNC or RDP support things like streaming video very well, but I guess that will come. A hybrid approach would be fine, too -- remote control, remote HTTP proxying, or all local, as the needs dictate.