Re: Thin clients

It depends Rob. If you are running a standalone application like Word running in a VM on the hypervisor and there was a new Word version that required changes to the hypervisor then yeah, there would be some issues. However, if the new Word version running in the VM on the hypervisor didn't require hypervisor changes, then the server would just serve up the new Word version. Period. Nothing else needed at the client end.

As others have mentioned, data persistence would be at the server end so that wouldn't be an issue.

Pete


rob@xxxxxxxxx wrote:

Sure, and you would have the same deployment issues as your basic fat client. Every time you needed to do an upgrade you'd have to upgrade the chips on all those clients to support the latest browser, Open Office application, etc.

Or, you could do what IBM tried and during bootup it would initiate a trivial ftp session (TFTP) to the mother ship and update itself from there. With huge cautions that if the user rebooted again during the update you just trashed the thin client.

What about cookies and that genre? Say what you will about the "black helicopters crowd" who insist on turning off all cookies, java script, etc. You know, those who insist that the world adopt to them (but doesn't).

Rob Berendt