Quoting Doug LaRue <[EMAIL PROTECTED]>:
Don't know but I'm always seeing talk of using ssh tunneling to gain performance comparable to NX. I've also seen people mentioning running
Heh.. lately I've been making my NX connections to work via an ssh tunnel (got tired of the vpn options) so my NX session is basically going through ssh inside ssh.
While ssh tunnels will allow much the same connectivity, you won't have the session reconnection ability.. unless you're ssh tunneling vnc or something. I tend to use the same session from home for weeks on end, reconnecting when needed.
One big advantage we can see with something like NX with clients in thin client hw at work is the ability for an engineer to go home and reconnect to the same login they just left. Sunray has some of this, but via a sunray at home with either a hw vpn box (pre sunray2) or a newer runray with vpn client built in. However that adds cost. Sun tried to write a sunray software client a couple years ago, but it was unusably slow (big shocker, it was also java, which was probably part of the problem). They supposedly have done somewhat better, but really, why bother at this point? Still uses shared display servers that even 1 user running just about anything on the server itself will cause slowdowns for everyone else connected to it. I'd rather segregate each user to their own virtual box that they can pound the crap out of.
NX would allow anyone with a computer at home (and I doubt we'd have more then a couple employees without one) to just run the NX software client at home. Or if they have a company laptop, they could use that at work and home and not even use a hw thin client.
-- Mike Marion-Unix/Linux Admin-http://www.miguelito.org Vir: "Londo, are you deliberatly trying to drive me insane?" Londo: "The Universe is already mad. Anything else would be redundant." ==> Babylon 5 -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
