Tag Archives: Chromoting
So this is being implemented likely to test its compatibility with Native Client. It’s also possible that it’s being used to test Chromoting, another experimental feature in about:flags that doesn’t work unless you are on the dev team for Chromium.
It’s been called Chromoting, but the fact that Google is partnering with companies that specialize in remote access tells me that perhaps that name is not going to be official at all.
Google and RealVNC have announced a partnership to provide remote access capability. According to the press release that was sent to me, this functionality is going to be built into both the browser and the operating system.
“With more than 120 million users around the world, Chrome’s focus on speed, simplicity and security has made it an exciting platform for innovation,” said Chee Chew, engineering director at Google. “We are thrilled to tap into RealVNC’s proven technology and expertise to complement our existing initiative.”
The launch of the Chrome OS platform is very dependent on Google having a number of other services available for users. After all, being a cloud operating system will require heavy usage of the web. So when reports started emerging of Google’s Cloud Picker service accidently being sent into the wild, I thought about how storage in Google Docs is not really going to suffice for media files and the like.
Despite my reservations for the name itself, Cloud Picker will find its place among yet-to-be released services like the Chrome Web Store, Chromoting and Cloud Print as an important facet for Chrome OS users. I’m excited to try it out.
The Stable build of Chrome is being released today, and there is a whole bunch of new improvements that come with this release. It’s the latest major update in Google’s six week release cycle for Chrome builds, and a lot of work has been to prepare the browser for next generation web application capabilities and security features.
Perhaps the biggest new feature is Chrome’s integration of a PDF reader that is based on the Foxit SDK. Just like Flash, it will be sandboxed to prevent vulnerabilities in PDF files to be able to exploit a user’s system.
When Chrome Program Manager Anthony Laforge said “things are going to start moving quite fast” with Chrome’s release cycles and features in about:labs, he wasn’t joking. Today’s newest Chromium builds feature a Cloud Print Proxy option in the Chrome Labs feature you can access by typing in “about:labs” into the Omnibox.
Another part of the description that was cut off by my screenshot says this, “Once this lab is enabled, you can turn Cloud Print on by logging in with your Google account in the Options/Preferences in the Under the Hood section.”
I was unable to find that option in the Under the Hood section of settings, so I’ll assume that it’s a work in progress. Features like this and Chromoting that require a Google Account sign in aren’t quite working, at least for public consumption. This new feature seems to go along with the other most recent new lab which was allowing background webapps to run, since Cloud Print also uses a background service to connect with Google’s print servers.
During the initial announcement of Chrome OS, many were concerned about printing capabilities in the cloud. Google countered this by introducing its Cloud Print API, whereby their servers would be used as proxies that contain all the hardware drivers needed to use a printer. Now that we see smartphones able to do this with the right app, it seems more of a solid reality than it was in the past.
Last night’s Google Chrome release announcement for the Beta channel has flipped over to version 7. One of the major updates is the Google Chrome Labs feature becoming available for the first time in this channel. This is in an attempt to move some features out of the command line switch and into an easier toggle method by using the “about:labs” command from the Omnibox for the menu of options.
One interesting other feature included for Macs is an expose-like showing of all open tabs. CNET’s Steve Shankland has a photo of this, which looks like a great feature that has been on display as a variety of extensions, but is integrated for Apple users.
The ability to remote into another machine via the Chrome platform is known as “Chromoting” and has been seen in Chromium OS for some time. However, it appears that Google’s Chromium engineering team is now putting Chromoting into the “about:labs” section of the most recent builds of the Chromium browser.
A lot is being said recently about the Chromium blog’s post that the newest version of Chrome will be sixty times faster that its current generation on the market. That is a major improvement in speed, and it shows just how much weight is being thrown behind the Chromium project in order to increase people’s ability to use the web faster.
Other browser makers are taking note, but it’s going to be hard to catch up to Google at this point. They are working on features that will improve user experience not only for the purposes of the browser but also for Chrome OS. Witness the fact that printing options are being improved, remoting features are being included and simple formatting tricks that eliminate the need for Notepad are showing that when the Chromium team sees a problem, they simply fix it.
Using other browsers, they do have some features that Chrome does not. Firefox, for example, is still really feature-rich and its interface has been much improved. But after using Google’s browser for a long period time the competition seems, well, slow. Has anyone else noticed this as well?
A while back it was reported that Chrome OS would feature a remoting system that would allow users to be able to access their favorite native applications that are on traditional operating systems. This would be similar to a remote desktop-type of situation.
Now, it appears as if that will become a reality now that “Chromoting” as a feature has shown up in the most recent Chromium (and Canary) builds.
If you want to see Chromoting as an option for yourself, get a new build of the Chromium browser and at the switch “-enable-remoting” to your desktop shortcut.
UPDATE: Changed this post to reflect that you can also do this with Chrome Canary as well.
The idea of Chromoting as a way to bridge the gap between the web-enabled environments of the future over to the old model of installed applications on Windows, Mac and Linux seems to fit with the overall theme of Chrome OS. That theme is to get away from natively installed applications, though many of us still will rely on these “legacy” apps to some degree.
In the smartphone realm, the use of remote desktop is possible to go into our computer at home or at work to do things. Chromoting will be no different than that, installed as an extension on a Chrome OS device with another application on whatever other machine you need to remote into.
As cloud computing in ramps up from an operating system standpoint, there is going to be some software that simply will not be available in the cloud. Although it is true when Google says that most major applications are coming out today arrive web-based, there are still some resource-heavy tasks that require a traditional computer. Chromoting thus offers power users the ability to possibly use virtualization on servers to harness both Chrome OS and whatever applications they may need directly through the cloud.
I can see a variety of uses for Chromoting, and not just as a stopgap solution for legacy purposes but also as a path to allow Chrome OS to act as a window to more process-intensive computing capabilities. One would not only be able to use it to access powerful software tools on a thin client Chrome OS device, but the enterprise would benefit as well. I could see IT support analysts, salespeople and health professionals utilizing Chromoting on a tablet or netbook to access resources in a safe and controlled way that perhaps other devices would be unable to.
What other intriguing purposes could Chromoting provide for that I have missed?
Chrome OS will run legacy PC applications using a process unofficially called ‘Chromoting’ according to the Register.
In a partnership with HP, a launch of cloud-enabled printers will be coming soon allowing your printing to be wireless in the cloud.
The Dell Linux team has updated their build of Chromium, specifically for its line of netbooks.
Interestingly, Apple has been credited with spotting some bugs in the Chrome browser.
ZDNet asks, what will be the effects of Android and Chrome OS on the release of Linux distributions?