Applies To:

Show Versions Show Versions

Manual Chapter: Establishing Additional TCP Connections with MultiConnect
Manual Chapter
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

Overview: Establishing additional TCP connections with MultiConnect

Most web browsers create a limited number of persistent TCP connections when requesting data, which restricts the amount of content a client can receive at one time. You can provide faster data downloads to your clients using the WebAccelerator™ system’s MultiConnect feature.

When enabled, the MultiConnect feature modifies embedded URLs with unique subdomains, prompting the browser to open more persistent TCP connections (up to two per subdomain generated by the WebAccelerator system). The origin web servers never get a request from these additional subdomains; they are used exclusively on embedded URLs or links that request images or scripts and are only for requests and/or responses between the client and the WebAccelerator system. If the WebAccelerator system needs to send a request to the origin server, it removes the subdomain prefixes before sending the request.

The WebAccelerator system uses the MultiConnect feature only on the following types of links:
  • Image tags: <img src="...">
  • Script tags: <script src="...">
  • Forms whose input type is an image: <form><input type="image” src="..."></form>

Optimization of TCP connections

The WebAccelerator™ system’s MultiConnect feature decreases the number of server-side TCP connections required while increasing the number of simultaneous client-side TCP connections available to a browser for downloading a web page.

Decreasing the number of server-side TCP connections can improve application performance and reduce the number of servers required to host an application. Creating and closing a TCP connection requires significant overhead, so as the number of open server connections increases, maintaining those connections while simultaneously opening new connections can severely degrade server performance and user response time.

Despite the ability for multiple transactions to occur within a single TCP connection, a connection is typically between one client and one server. A connection normally closes either when a server reaches a defined transaction limit or when a client has transferred all of the files that are needed from that server. The WebAccelerator system, however, operates as a proxy and can pool TCP server-side connections by combining many separate transactions, potentially from multiple users, through fewer TCP connections. The WebAccelerator system opens new server-side connections only when necessary, thus reusing existing connections for requests from other users whenever possible.

MultiConnect example

For this example, your site serves a simple page (http://www.siterequest.com/index.htm) that consists of several image files. The page that your site serves appears as follows:

<html> <head><title>example page</title></head> <body> <p>The images that your site serves:</p> <p><img src=”myImages/image1.jpeg”></p> <p><img src=”myImages/image2.jpeg”></p> <p><img src=”myImages/image3.jpeg”></p> <p><img src=”myImages/image4.jpeg”></p> </body> </html>

An additional subdomain prefix of wa is configured for the host map and the MultiConnect feature enabled, so the WebAccelerator™ system modifies the page and serves it as follows:

<html> <head><title>example page</title></head> <body> <p>The images that your site serves:</p> <p><img src=”http://wa1.www.siterequest.com/myImages/image1.jpeg”></p> <p><img src=”http://wa2.www.siterequest.com/myImages/image2.jpeg”></p> <p><img src=”http://wa2.www.siterequest.com/myImages/image3.jpeg”></p> <p><img src=”http://wa1.www.siterequest.com/myImages/image4.jpeg”></p> </body> </html>
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

Was this resource helpful in solving your issue?




NOTE: Please do not provide personal information.



Incorrect answer. Please try again: Please enter the words to the right: Please enter the numbers you hear:

Additional Comments (optional)