Google reveals plans for Chrome cloud synchronization

Google has revealed plans for a Chrome cloud service that will allow users to synchronize browser data with their Google accounts. The synchronization framework, which is still at an early stage of development, will arrive in Google's open source Chromium project later this week. Google says that a Chrome build with the sync feature enabled could be made available through a dev-channel update this month.

In a message posted to the Chromium developer group, Google engineer Tim Steele described the process through which the feature will be integrated into the browser. Google has also published a design document that provides a high-level overview of the synchronization architecture.

"A bunch of us have been working on a feature to sync user data in Chromium with a Google account," Steele wrote. "We have built a library that implements the client side of our sync protocol as well as the Google server-side infrastructure to serve Google Chrome users and synchronize data to their Google Account."

The Chrome synchronization framework will initially handle bookmarks, but it is designed to support other kinds of browser data in the future. It uses a push messaging model to propagate change notifications, which means that activity in one instance of the browser will be reflected immediately in other instances. This will make it more seamless than other bookmark synchronization services like Weave and XMarks that rely on polling to determine when data needs to be synchronized. Google also plans to provide a Web interface so that users can remotely access their bookmarks from any browser by logging into their Google accounts.

The synchronization framework will use a persistent XMPP connection for change notifications. The Google Talk servers will provide the backend infrastructure for that part of the synchronization process. The actual bookmark data will be transmitted in Google's Protocol Buffer format. The design document suggests that XMPP was adopted instead of a polling model for scalability reasons and to make synchronization more seamless.

Steele says that the sync code represents a major change to the browser's code base and that it will be landing in the Chromium tree incrementally so that it can be properly reviewed. The client-side sync code currently works on Windows and Linux but doesn't work yet on Mac OS X. To enable broader testing, the developers plan to make available an experimental Chrome build for Windows with the synchronization feature enabled; it will be deployed through the developer update channel later this month.

"We're planning to use the syncapi DLL to produce a sync-enabled Google Chrome build for dev-channel users in a week or so, to get the feature into experimentally inclined hands," Steele wrote. "We have a great deal of infrastructure, both in the browser and in the form of production Google services, that needs to start seeing real user traffic and usage. It takes a great deal of testing and confidence inspired by real usage statistics before any complex system like this can be deemed adequate for use by a large user base."

Browser sync will boost the value of Google's browser and advance Google's strategy of converging the desktop with the cloud. It's a particularly intriguing development in light of Google's upcoming Chrome OS. Seamless synchronization of browser data between a desktop and netbook could be a very compelling feature. It's not clear yet if Google will also bring this feature to its Android mobile browser, but it seems like an obvious move.

Google intends to document the protocols and make the client-side source code available under an open license, which means that it could be possible for third-party developers to bring Google synchronization support to other browsers. This will be a welcome development for users who still mourn the loss of Google's Firefox browser sync, which was discontinued last year.
http://arstechnica.com/open-source/news/2009/08/google-reveals-plans-for-chrome-cloud-synchronization.ars

What Do You Expect from Google Chrome OS?

I've asked some time ago the readers of this blog what they expect from Google Chrome OS, an open-source operating system built around Google Chrome, that will be released later this year. Here are some of their answers:

Integration with Google Accounts

"I believe Google accounts will be used to login to Chrome OS. Kinda whereever you go, you can use your Google account username/password to login. I hope it will use local disk to store frequently accessed file and sync it to Docs like Dropbox."

It should work offline

"There would have to be some kind of offline credential caching so you can log on even when you are not connected to the network."

Instant boot

"The thing I need with Google Chrome OS is instant bootup. I want something where I open up my laptop and the screen turns on and puts a web browser in my face."

It should be fast

"I just want to get rid of infinite waiting for load up. When I turn on my computer, half the times is just to open a web browser, a media player and an instant messaging program. I don't want to have to wait AGES for all sorts of background programs and services to load up."

Built-in desktop search

"I like the desktop search element of Google Desktop: it's a good way to access my files, e-mails and web history quickly. That should be included in Chrome OS. And there should be an offline cache of everything, so that I can still see read web pages I've visited even when offline."

In sync

"Syncing is important these days. Not just bookmarks, but passwords, and "user states" so you can pick up on another machine almost where you leave off on one. I would be able to start working on a document on my desktop machine and then switch to my laptop and hit the road, confident that when i open the document authoring app I'll be right where I left off."

Invisible

"Google ChromeOS should save screen real estate. On smaller devices like netbooks, you need to conserve as much screen real estate as possible."

Use applications without installing them

"Even if storage memory is cheaper now than ever, mobile phones, netbooks, etc. will benefit of avoiding to install software specific for each use on the physical memory and maintaining it "in the cloud". Sites should have the capability (and maybe a standard protocol) to communicate each other with the browser as a medium (avoiding the download and following upload of the object), user should have the capability to chose the service that he wants to subscribe to (eventually choosing it from an online appstore-like site), the OS should be able to recommend new and interesting service to subscribe to the user based on information collected (with his permission) about his behaviour."

Run Windows applications

"I want to run Windows programs, as well as games. I want Chrome OS to be able to do everything a normal computer can do! That way I can get ditch Windows and get Chrome OS for (hopefully) free!"

Don't forget the hardware!

"Driver support for a wide range of mobile hardware -> platform hardware combination. I'm particularly interested in WiMax support on an ARM processor."

So people want a fast operating system that loads instantly, doesn't use too many resources, saves your data online so you can continue your work from another computer and it keeps the data in sync, works offline, uses applications without installing them, runs Windows applications and it's compatible with many combinations of hardware.

What do you expect from Google Chrome OS?
http://googlesystem.blogspot.com/

Google building 3D hardware boost into Chrome - Web News

Google building 3D hardware boost into Chrome - Web News: "Departing significantly from what other browsers offer, Google has begun building its O3D plug-in for hardware-accelerated 3D graphics into its Chrome browser.
“The O3D team is working on getting O3D integrated into the Chromium build, and we’re close to being able to complete our first step towards integration,” said programmer Greg Spencer in a mailing list announcement Wednesday about Chromium, the open-source project that underlies Chrome itself. “I’ll be making the Windows build of Chromium be dependent upon building O3D as part of the build process.”
By helping to pave the way for high-powered Web-based games, the move furthers Google’s ambition to speed the transformation of the Web from a static medium into a foundation for applications. Another piece of the work is Google Native Client, which is designed to let Web applications take advantage of a computer’s native processing power.
The overall effort has taken on new importance with the announcement of Chrome OS, Google’s Chrome-based operating system set to arrive on Netbooks in the second half of 2010. Chrome OS will use Linux under the covers, but the real foundation for Chrome OS applications is the Web, Google has said.
Native Client coming, too
Google plans to build Native Client into Chrome, too.
“We recognize that there is well-justified resistance to installing browser plug-ins. For this reason, we have a strong preference for delivering Native Client pre-installed or built into the browser, and we’ll be focusing on that as our main strategy for delivering Native Client to users,” said Brad Chen, engineering manager of the Google Native Client effort, in June."
http://www.allfeedz.com/3094/google-building-3d-hardware-boost-into-chrome-2

Google gets set to shatter Windows’ dominance Google’s operating system escalates Microsoft duel

SUN VALLEY, Idaho —- Google Inc. is hoping to gain greater control over how personal computers work by developing a free operating system that will attack Microsoft Corp.’s golden goose —- its long-dominant Windows franchise.

The new operating system will be based on Google’s 9-month-old Web browser, Chrome. Google intends to rely on help from the community of open-source programmers to develop the Chrome operating system, which is expected to begin running computers in the second half of 2010.

The early versions of the Chrome operating system will be tailored for “netbooks,” a breed of low-cost, less powerful laptop computers that are becoming increasingly popular among budget-conscious consumers primarily interested in surfing the Web.

That is a direct challenge to Microsoft, whose next operating system, Windows 7, is being geared for netbooks as well as larger computers.

The vast majority of netbooks already run on Windows, and that is unlikely to change unless Google can demonstrate the Chrome operating system is a significant improvement, said Forrester Research analyst Paul Jackson. He noted that many customers had returned the original netbooks that used open-source alternatives to Windows.

“People wanted Windows because they knew how to use it and knew how applications worked.”

Google struck a confident tone in a blog posting late Tuesday night announcing its operating system. The Mountain View, Calif.-based company believes it can streamline the operating system to improve speed and reduce security threats.

“We hear a lot from our users and their message is clear —- computers need to get better,” wrote Sundar Pichai, Google’s vice president of product management, and Linus Upson, its engineering director.

Microsoft hadn’t responded to requests for comment through Wednesday.

The success of the Chrome operating system will likely hinge on its acceptance among computer manufacturers that have been loyal Windows customers for years, said Matt Rosoff, an analyst for the research group Directions on Microsoft. “Most people, when they get a new operating system, they get it with their PC,” he said. “I don’t think most people think much about their operating systems.”

Getting consumers and businesses to switch to computers powered by a new operating system won’t be easy, as Google has learned from the introduction of Chrome. Google says about 30 million people are using Chrome, a small fraction of the Web surfers who rely on Microsoft’s market-leading Internet Explorer.

Microsoft’s Windows operating system has been even more dominant for a longer period time despite challenges from Apple Inc. and various systems based on Linux, the same type of open-source software that Google plans to use.
http://www.ajc.com/services/content/printedition/2009/07/09/google0709.html

Google Drops A Nuclear Bomb On Microsoft. And It’s Made of Chrome.

Wow. So you know all those whispers about a Google desktop operating system that never seem to go away? You thought they might with the launch of Android, Google’s mobile OS. But they persisted. And for good reason, because it’s real.

In the second half of 2010, Google plans to launch the Google Chrome OS, an operating system designed from the ground up to run the Chrome web browser on netbooks. “It’s our attempt to re-think what operating systems should be,” Google writes tonight on its blog.

But let’s be clear on what this really is. This is Google dropping the mother of bombs on its chief rival, Microsoft. It even says as much in the first paragraph of its post, “However, the operating systems that browsers run on were designed in an era where there was no web.” Yeah, who do you think they mean by that?

And it’s a genius play. So many people are buying netbooks right now, but are running WIndows XP on them. Windows XP is 8 years old. It was built to run on Pentium IIIs and Pentium 4s. Google Chrome OS is built to run on both x86 architecture chips and ARM chips, like the ones increasingly found in netbooks. It is also working with multiple OEMs to get the new OS up and running next year.

Obviously, this Chrome OS will be lightweight and fast just like the browser itself. But also just like the browser, it will be open-sourced. Think Microsoft will be open-sourcing Windows anytime soon?

As Google writes, “We have a lot of work to do, and we’re definitely going to need a lot of help from the open source community to accomplish this vision.” They might as well set up enlistment booths on college campuses for their war against Microsoft.

Google says the software architecture will basically be the current Chrome browser running inside “a new windowing system on top of a Linux kernel.” So in other words, it basically is the web as an OS. And applications developers will develop for it just as they would on the web. This is similar to the approach Palm has taken with its new webOS for the Palm Pre, but Google notes that any app developed for Google Chrome OS will work in any standards-compliant browser on any OS.
What Google is doing is not recreating a new kind of OS, they’re creating the best way to not need one at all.

So why release this new OS instead of using Android? After all, it has already been successfully ported to netbooks. Google admits that there is some overlap there. But a key difference they don’t mention is the ability to run on the x86 architecture. Android cannot do that (though there are ports), Chrome OS can and will. But more, Google wants to emphasize that Chrome OS is all about the web, whereas Android is about a lot of different things. Including apps that are not standard browser-based web apps.

But Chrome OS will be all about the web apps. And no doubt HTML 5 is going to be a huge part of all of this. A lot of people are still wary about running web apps for when their computer isn’t connected to the web. But HTML 5 has the potential to change that, as you’ll be able to work in the browser even when not connected, and upload when you are again.

We’re starting to see more clearly why Google’s Vic Gundotra was pushing HTML 5 so hard at Google I/O this year. Sure, part of it was about things like Google Wave, but Google Wave is just one of many new-style apps in this new Chrome OS universe.

But there is a wild card in all of this still for Microsoft: Windows 7. While Windows XP is 8 years old, and Windows Vista is just generally considered to be a bad OS for netbooks, Windows 7 could offer a good netbook experience. And Microsoft had better hope so, or its claim that 96% of netbooks run Windows is going to be very different in a year.

Google plans to release the open source code for Chrome OS later this year ahead of the launch next year. Don’t be surprised if this code drops around the same time as Windows 7. Can’t wait to hear what Microsoft will have to say about all of this. Good thing they have a huge conference
http://www.techcrunch.com/2009/07/07/google-drops-a-nuclear-bomb-on-microsoft-and-its-made-of-chrome/