Slashdot Mirror
Jumping From Computer To Computer
Roland Piquepaille writes "Imagine a world where computers become so ubiquitous that the idea of carrying a laptop will almost be laughable, a world where any computer could be your computer! According to the Pittsburgh Post-Gazette, this is the goal of Intel Research Pittsburgh's Internet Suspend/Resume (ISR) project, a project that may one day let your work jump from computer to computer without interruption by using the Internet, distributed file systems, and virtual machines. When the non-proprietary technology becomes available, a user will suspend a task on the computer he's working on, and resume this work using another computer in another part of a city or several thousands of miles away. The second system will look identical to the first one, with the same files and applications opened. This technology would also ease OS upgrades or eliminate the pain coming from a hard disk failure. The project has even a feature named Rollback which would permit to go back in time, eliminating these pesky viruses. A pilot test will start this fall, so don't expect to be able to use ISR for a while. You'll find more details and references in this overview."
I use scripts to sync my work all the time. I don't see what the big deal is here.
Screen over SSH :)
While the article refers to the idyllic view of being to work anywhere, the tech exists already. In a corporate environment with Win2K/NT4, there's roaming profiles.
There's also Citrix and Terminal Services which allow to have that experience throughout a LAN. Tie it up with a SSL-VPN solution and then you have that environment anywhere in the globe.
Take it from someone who's had their EBay account hijacked not once, but twice. Beware public terminals!
OK, I read enough of the article:
If a user's computer becomes infected, she could use the Rollback feature to go back to an arbitrary point in time prior to the infection and resume work there, deleting the subsequent work -- and the virus.
So I was right with my original assumption, if the virus simply hangs low for x days you rollback and still lose x days work.
Well, with Sun's 'sunray' stuff. YOu carry a smart card, pop it in, do your work. Mid work, pull the card, and the screen goes blank. Pop the card in another computer, and your work is still there.
The future is 10 years ago.
Well, with Xterminals... dummy boxes with small system image, loading a desktop off the central server.
The future is 20 years ago.
Well, with mainframe technology, and 3270 terminals.
Zapman
There are three types of Sun Ray session mobility. The first is session mobility on the same Sun Ray server. This is simply redirecting the display to another thin client. The second is migrating the session to another server in the Sun Ray server cluster. This involves actual replication of user state. The third is global session mobility, which takes the cluster example and applies it to the WAN. Because global session mobility first replicates user state (such as unix . files) to the local Sun Ray server, it can take a few minutes. Also, global session mobility uses NFS over the WAN so files continue to be stored on the file server at the users primary office. This latter fact can slow down software dependent on locally stored files that do not get replicated automatically (such as Mozilla bookmarks).
None of this requires the use of a Javacard. The Javacard is optional.
The ISR capability described could significantly enhance the current PC-centric thin-client market. First the PC-centric thin-clients were defined by Windows Terminal Server. Now, to address WTS' limitations, some vendors are pushing "blade PCs". However, it seems PC sessions running in VMs on a SMP server is inherently more flexible and manageable than a blade server for each client, and at the same time offers more isolation than WTS.
All of these programs let you access a machine remotely, but screen & VNC allow you to keep a particular session alive while you access it from different locations. With remote X (or telnet), if you want to access the server from a different location, you have to log in again, starting a new session. With screen or VNC, you are continuing an already opened session. Any programs that you were running are still there, unchanged. Read up on VNC a little more and try to understand the implications of this feature. It really is a nice feature, above and beyond what X provides.
I'm a leaf on the wind. Watch how I soar.
Maybe, 50 years from now, everyone will have fiber
First, read what I wrote: Some day soon this will be common. While it is not "common" now, it is becomming more common.
Second, I seriously do not think it will be "50 years from now". This is not the same as "flying cars", this is real technology that is actually happening.
Also, starting a discussion / argument / statement with "um" immediately takes away half of the discussion / argument / statement's validity.
"Who are in control, they are not in control of anything - they don't even control themselves!" - Glen Beck
That's what I often carry instead of a laptop.
It's just as simple as that: mounting my drive into a random OS installation would give me a huge fit of paranoia every time I'd have to do that. Plus, I have a perfect control of which OS version is on my CD.
The only drawback is, you can't put a Windows installation on a live CD, so I still have to bring a laptop if I need Windows.
You can't just walk away from your desk with an X session, and resume at another location. You can do exactly this with vnc. Your applications don't have to close, or anything. The problem with X is that the "X server" is running on the terminal. You can't close the X session without closing all the X-clients, but you may not want to close them. When you run a VNC session, there is a virtual X session running, so you can relocate the X session to any other terminal.
I mean, even with the SunRay, it's like, whoo-hoo, we combined VNC and H.263 and you should jump for friggin' joy.
;-)
Actually, Sun Rays are really much more advanced than VNC. A bit more like Citrix ICA. Either way, it's cool technology. Just because Sun has packaged it better than everyone else doesn't invalidate their claim on the market. Personally, I'd love to have a Sun Ray network. I could take my smart card and work anywhere I want. No being tied to a desk with really bad lighting. I'll just take the comet downstairs to the Starbucks and actually get some work done!
I don't think anyone really wants this.
Actually, I think Sun's biggest problem is how expensive it is. I know of many people who would love to buy a used Sun machine and a few Sun Rays just to wire their house. But when their software costs more than the machine, you know you've got a problem. That's the same thing that killed NT Terminal Server. Citrix ICA was doing quite well with WinFrame until Microsoft pulled a fast one on them.
I think a visual protocol is too specific. The work needs to be in creating a widget/RPC API that lets you splat a standardized local GUI onto remote application servers.
Myself and others have spent a lot of time trying to figure out the best way to do this. I did some on renovating AppliWeb up until XWT showed up. So far, XWT seems to be the best option. We'll see what the future holds, though.
Javascript + Nintendo DSi = DSiCade
Looking at all the posts about Sun Rays, VNC over SSH, remote X, and "what if someone hijacks your session", I am absolutely amazed at how many people here seem to completely misunderstand this concept.
1. Sun's Sun Ray is a glorified terminal. All processing takes place on the server, and the resources of the terminal itself are almost non-existant. From Sun's website "Compact, fanless plug-and-work device that processes input and output and manages communication with the shared Sun Ray server." These might be nice if the price stated about $99, not $359. And if I could run the server end on a Linux box (cluster), not some ungodly expensive Solaris behemoth. [Okat, the SunFire v210 isn't expensive, but who the hell wants a 1 GHz UltraSpark IIIi cu to run stuff like this?]
2. VNC over SSH/Remote X. Same issues as the Sun Ray -- not using local resources. You're running everything on a remote server. NOT what the article is describing at all.
3. Hijacking a session, security, etc. Yes, a concern, but it is a totally separate issue. How about keeping a super check, super small USB key with you that has a personal certificate. Then, encrypt all communication between your location and the main servers using that? There are plenty of solutions to this problem.
What this article is talking about using local resources (CPU, sound, 3D acceleration, etc.) to do the task but combine it with a distributed file system. Use the "local" hard drive as a file system CACHE, to speed things up.
Use the "local" CPU and RAM to run programs, not some server on the other side of the world. This way you can run DISCONNECTED or not consume mega networking resources.
Think "IMAP in disconnected mode" or "web browsing while offline".
Sun (and Oracle, IIRC) both eschew this "three tier" client server system in favor of true terminal server sessions. However, terminal sessions, including things like VNC, are too limited when it comes to tasks like 3D display.
By combining the best of terminals (state saved computing) with the power and responsiveness of local resources (think "desktop PC"), they have a lot of potential.
They also have some major hurdles to overcome. Complete hardware abstraction is one. Differences in hardware capabilities, etc. are not trivial problems. (Go from 1280x1024 w/5.1 surround to a 800x600 screen w/o speakers and see how it handles it.)
-Charles
Learning HOW to think is more important than learning WHAT to think.
This is the idea behind FirstClass (from the artist formerly known as Softarc, then Centrinity, now the FirstClass division of OpenText). Longtime Mac users, Scandinavians, or alumni of certain universities may recognize what I'm talking about.
FirstClass is a multiplatform client-server setup that incorporates intra- and internet servers (WWW, email, etc.), groupware (conferencing, calendaring, shared resources, file and contact management, etc.), instant messaging, and the best unified messaging I've ever seen. It's like a more capable version of MS or Novell groupware, plus unified messaging, but way more manageable and scalable (think 100 000 users on an NT4 box administered by one part-time administrator, just for one example).
Why it's not better known is quite beyond me. Don't take my word for it, though; download the free trial and check it out for yourself. It's not time-limited or anything, it's not crippleware - it's a full-function server. The only limitation is licenses (you get five user licenses, any more have to be purchased).
And no, I don't work for them. I don't even stand to gain financially from increased business. I just think, based on what I've seen, that it's a great product. Cheers!
Corruptissima re publica plurimae leges.