A Google engineer recently posted a message on the Chromium development board stating that his team would be implementing a synchronization service into Chrome’s open-source progenitor as early as this week. What’s different about Chrome’s sync service? It uses a “push” service, through Google Talk protocols, to instantly move bookmarks, settings, and other user data into a Google account base, where it could be accessed on the web from any browser. A developer channel build of Chrome with some of the first features implemented can be expected as early as the end of this week, according to the posting. Does a push-synchronized Chrome change your view of each web browser’s strengths and weaknesses?
Source : Ars Technica
Tags: engineer, google, open source, protocols, strengths and weaknesses, sync service, synchronization service, web browser