On 04/21/2013 08:09 PM, Edward Ned Harvey (blu) wrote:
From: [email protected] [mailto:discuss-
[email protected]] On Behalf Of Tom Metro
VNC? I've done plenty of remote coding via SSH, but not VNC. What's the
underlying circumstances that are motivating that choice?
In my case: Users want an IDE. They also want to be able to suspend / resume
their remote session, and simply continue after they get home or whatever.
They want to be able to reboot and sleep their laptops, and travel, without
losing context.
Yes, if you can offload the build process to their laptop, that's great. But
there are a lot of reasons people might not want to do that.
VNC allows for this. The login is done locally on the server by the VNC
server process. The VNC client simply connects. So, you can start a
build while in the office logged in via your laptop. You can close the
VNC client (or the PC sleep will cause it to close). At home, start up
your VPN, start your VNC client (We use UltraVNC) and the build will
still be running or will have finished. This is another advantage of VNC
over Putty/Exceed (not excel - I mistyped).
--
Jerry Feldman <[email protected]>
Boston Linux and Unix
PGP key id:3BC1EB90
PGP Key fingerprint: 49E2 C52A FC5A A31F 8D66 C0AF 7CEA 30FC 3BC1 EB90
_______________________________________________
Discuss mailing list
[email protected]
http://lists.blu.org/mailman/listinfo/discuss
