HTTP was the workhorse on the web for over a decade. But it was designed at a time when the applications were written very differently and are not too complex. The Web today has come a long way with the content files is rich, multi-media, JavaScript, and mobility support. Unfortunately HTTP has not kept pace and needs a refresh for mobile applications and other.
To reduce the use of bandwidth, making Internet communications faster and accelerate the use of loading time of a new compatible bi-layer HTTP is increasingly in popularity. It is known as SPDY and is a protocol (SSL) encrypted Session Layer introduced for the treatment of light HTTP. SPDY is not an acronym; it is the full name of an open network protocol for transporting Web content. The goal of SPDY is to reduce web page load time using a single TCP connection per domain. SPDY achieves this by allowing the intertwined resource requests and prioritizing between resources.
SPDY provides a number of advantages over standard HTTP connection. It transmits fewer packets and therefore reduces packet loss and reduces the ballooning of the buffer on the intermediate routers. It also requires fewer TCP connections and uses these connections more efficiently. For example, redundant headers are removed, other headers are compressed, and it supports the priority application. SPDY manages asynchronous interleaved to prevent blockage of the router. SPDY also realizes reduced latency by leveraging content compression. HTTP performance improvements result on the beach from 27 to 60 percent in load times without encryption and 39 to 55 percent with SSL. These gains are even more evident when customers see the packet loss rate of over 2 percent common in mobile environments.
Although most browsers support SPDY server infrastructure today / to still operated largely on HTTP application. With the introduction of SPDY a number of problems arise from this shift: the layer 4 of treatment should take place; security best practices are broken; and capacity planning is affected. The promises of this protocol will not be satisfied. A networking device which can transform SPDY HTTP messages is necessary. This gateway functionality allows the optimization layer 7 and provides time for data centers to move to support SPDY. SPDY is slowly changing as a protocol increasingly popular websites can adopt without having to rebuild their existing infrastructure.
NetScaler Application Delivery Controller provides complete integration of this gateway functionality in all editions and software platforms (MPX, VPX and SDX). These devices acts as a proxy and to ensure communication HTTP clients and servers as well as SPDY sessions and transform them. Incoming requests are stripped of their SPDY layer and server responses have added SPDY encapsulation. No loss of functionality is engaged in the execution of this gateway. For example, the full content of layer 7 switching and data analysis continue to be available. NetScaler also supports Protocol Next Negotiation (NPN) which is required for SSL modules used with SPDY gateway functionality. Extensions for NPN TLS are also included.
That is really nice to hear. thank you for the update and good luck. cannazon market
ReplyDelete