The server must open a socket, allocate memory for the user, acknowledge the user's HTTP request, fetch the data from disk memory, return the data, and close the session. The entire process is initiated again with the next mouse click. Most typical web pages include 15-20 objects. The most obvious result of this is Web latency. Content updates and requests require access to origin sites across the entire network - causing delays for downloads and data transfer.
Large transfers can take several minutes, adding long waits and cutting into user productivity.
A load balanced VIP typically involves different servers providing different content - for example, one pool of servers with static HTML content, another pool with GIF encoded pictures, and yet another pool with dynamic ASP content. Consider the case of a client connected to this VIP and expecting HTTP 1.1 support. The client is programmed to send successive GET requests to the VIP using a single TCP connection. The problem arises when these requests are for content provided by different servers. For example, suppose the client downloads an index.html page that contains includes statements for two GIF files and an ASP file.