Kindle Fire Silk Browser for Android Devices
January 4th, 2012 by reviewspecs. 1 CommentKindle Fire Silk Browser for Android Devices – The Kindle fire’s browser is now focusing the Android devices. Amazon designed the Kindle Fire’s browser, Silk, so that it can predict which pages will be visited by the user and pre-loaded on its cloud infrastructure. A developer has to focus on other Android devices, despite the questions posed by its operation.
Kindle Fire Silk – Browse Faster
One of the major innovations of the Amazon Kindle Fire Silk, it is able to guess the next page the user will visit and thus the load before the visit for faster browsing. To do this, Amazon is based on an architecture realizing the calculations and pre-loads on its cloud infrastructure, improving the user experience but raises real questions about the privacy and control that can perform on Amazon pages visited.
Nevertheless, a developer has just completed a port of Silk to the browser running on other terminals equipped with Android. To do so will require that the device is root and it is not already running Android 4.0 Ice Cream Sandwich. The port should also work under CyanogenMod 7.
Kindle Fire Silk Browser for Android Devices
Again, an advisor to save its data before trying this browser since it was not officially brought by Amazon. However, the first returns Announce operating safely on the Motorola Atrix and Droid X, for example. The front end of the Silk browser of Kindle Fire uses Webkit as a rendering engine and JavaScript V8 engine.
At the protocol level of the Silk-client communicate on the Kindle Fire Silk server via HTTP instead of SPDY (Speedy), a TCP-based protocol that is being developed by Google and supported by, for example, Google’s Chrome browser. The SPDY transmissions are encrypted using TLS and compressed with gzip. Multiple simultaneous transmissions, should greatly expedite requests. The “accelerator” feature of Silk can also be disabled on the client side of the Kindle Fire. The communication is then carried via HTTP (S).














January 5th, 2012 at 5:09 pm
[...] Read more … Like this:LikeBe the first to like this post. [...]