Linked by Eugenia Loli-Queru on Sun 17th Jun 2007 23:52 UTC
"For the purpose of this article, just like the first one, a WebOS is defined as virtual operating system that runs in a web browser environement. Don't like WebOS? Well, call it OnlineOS, or WebTop if you like. So, here is a review of another 10 functional WebOS', as well as some additional similar services which show promise but aren't launched or fully realized yet." More here.
Thread beginning with comment 248742
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2005-07-11
If your ISP simply blocks ports, use your remote desktop protocol of choice over port 80 (or any other open port). If they're wasting their resources on analyzing packets to see the actual protocol, tunnel your session through HTTP >:)
There's a great chance they allow SSH, though, which is much easier to use for tunneling, not to mention it's actually desirable in the first place.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2007-06-07
"The question, however, is why would you want to run a server based desktop through you crappy web browser, when the far, far, FAR superior X11 protocol has done exactly this for the last 20 years? "
The reason you would want to is the same reason we all now run PCs on our desktops instead of terminals. When corporate policy and corporate admins (for good or bad) lock down the resources that you need to be happy and/or successful at work, people start looking for other ways to accomplish what they need and want. The mainframes that were available when the personal computer was just gaining momentum, were vastly superior to any PC you could get your hands on. The problem was that it might take you a week to get access to run your code, if you could convince the admin to put it on the mainframe to begin with.
So, what did people start to do? They brought in their Apple IIs. They got twice as much done as the guy that was going the official route, and the desktop computer flourished.
Right now, we are in a similar phase. Admins are locking down desktops to run only corporate certified software. They are restricting ports on internet access, and users are looking for ways around this. Is running an Operating Environment over the HTTP an inferior method than using RPD or X? Sure, if you can make an RPD or X connection through the corporate firewall. But when the only protocol that the corp firewall will allow through is HTTP, a WebOS starts to look a lot more viable.
Heck, with the way ISPs behave these days, we may be faced with a 'WebOS' as the only kind of remote desktop that works.