Chrome beta for Android delivers a proxy-based speed boost, now syncs autofill and saved passwords

DNP Chrome beta for Android updated with autofill and saved password sync

As Google continues to work on improving Chrome for Android, today’s update for the company’s beta build of its browser appears to be a step in the right direction. Aside from the usual stability improvements and bug fixes, version 26.0.1410.26 adds two major additions. Lurking within this new software update is a data compression feature powered by Chrome for Android’s recently uncovered SPDY-powered proxy boost. When enabled, this feature optimizes HTTP traffic over an SSL connection and transcodes images to Google’s homegrown WebP format to reduce file sizes. In addition to turning your browser into a speed demon, this optional setting also uses Safe Browsing, which checks the sites you’re visiting against a list of potential threats for malware and phishing.

Further focusing on efficiency, this new update adds the ability to sync autofill and saved passwords across mobile devices. Google says it will deploy this new feature “in the coming days” and notes that you’ll also need the latest version of Chrome’s desktop beta in order to successfully sync your account. So, with that said, we suggest you wait at least a day or two before using your smartphone to go on a shopping spree, because those online checkout forms can be downright tortuous.

Filed under: , , ,

Comments

Source: Google (1), (2)

Chrome for Android build may tout a proxy-based speed boost

Chrome for Android on Galaxy Note II

A fast smartphone will only go so far toward improving browser load times if the connection isn’t there to back it up. If a discovery within a recent build of Chrome for Android is any hint, Google may have its own solution to that bottleneck. New code flags reference Google-run proxy servers that would squeeze pages using SPDY, improving performance at least slightly for the bandwidth-deprived. While there’s not much more to go on, the finding is enough to suggest that roughly equivalent boosters like Amazon Silk and Opera Turbo could have a real fight on their hands. We’d advise caution when the flags are only accessible by running an ADB command — they’re clearly not ready for prime time. Should Google flick the switch on compression for Chrome’s main release track, though, Android users may not need a third-party browser to sip the web through a thin straw.

Filed under: , , , ,

Comments

Via: François Beaufort (Google+)

Source: Chromium.org

Opera 12.10 browser hits desktops with Windows 8 touch, Retina display, SPDY support

Opera 1210 browser hits desktops with Windows 8 touch, Retina display, SPDY support

Opera has just released version 12.10 of its browser for Windows, Linux and Mac with some significant touch-ups, considering it’s a point release. Building on the recent 12.0 launch, the desktop browser now has OS X notifications, Retina support, pinch zoom and inertia scrolling for touch-friendly Windows 8, better color rendering, SPDY support for faster page loading and built-in page sharing to Twitter or Facebook. Along with a bump in speed, some of those new treats might tempt desktop users to make a switch, though it’s got an uphill climb. You can grab it at the source.

Filed under: ,

Opera 12.10 browser hits desktops with Windows 8 touch, Retina display, SPDY support originally appeared on Engadget on Tue, 06 Nov 2012 11:03:00 EDT. Please see our terms for use of feeds.

Permalink TNW  |  sourceOpera  | Email this | Comments

HTTP standards group looks to SPDY protocol to influence HTTP/2.0

Google’s SPDY protocol is already gaining traction among web browsing heavyweights such as Chrome and Firefox, but its next step may be its biggest showing to date — albeit in a different form. According to Mark Nottingham, the chairperson of the committee behind the HTTP protocol, a decision was made to focus on SPDY as the starting point for HTTP/2.0 discussion. Now, in case you couldn’t tell, this is far from a sure thing, and as is, the HTTPBIS Working Group is currently targeting 2014 for the new specification’s release. The decision is important, however, as the group seems intent to not reinvent the wheel with HTTP/2.0.

While Nottingham made it clear that SPDY wouldn’t serve as an outright replacement for HTTP — for example, the “methods, status codes, and most of the headers” will remain the same — there’s now a high likelihood that SPDY will heavily influence the new protocol. Up next, Nottingham will open the discussion to the group’s mailing list, and after that, approval will be sought from the Internet Engineering Steering Group (IESG). Once those steps are out of the way, however, we can expect work to begin in earnest toward the development of HTTP/2.0, and hopefully, a lot of speedy influences.

Filed under:

HTTP standards group looks to SPDY protocol to influence HTTP/2.0 originally appeared on Engadget on Tue, 07 Aug 2012 07:48:00 EDT. Please see our terms for use of feeds.

Permalink TechCrunch  |  sourceMNot’s Blog  | Email this | Comments