For example, router can't classify traffic by URL, treating all flows the same at the web site. Upgrading Web Servers Hardware improvements, server software, and HTTP protocols have caused the bottleneck to move away from the server, out to the access link. The PacketShaper Solution Traffic bottlenecks form at access links when a fast LAN pipe narrows into a slower WAN link, which causes multiple traffic sources to compete for limited capacity. This is where PacketShaper makes a difference. Imagine putting fine sand, rather than gravel, through a network pipe.
Sand can pass through the pipe more evenly and quickly than chunks.
PacketShaper conditions traffic so that it becomes more like sand than gravel. These smoothly controlled connections are much less likely to incur packet loss and, more importantly, the end user experiences consistent service. As you'll see in the next section, PacketShaper offers predictable performance by taking advantage of TCP's own mechanisms to overcome TCP deficiencies. Where TCP relies on tossed packets to infer congestion, PacketShaper provides direct feedback to the transmitter by detecting a remote user's access speed and network latency and using this data to optimally pace transmission. This results in smoothed traffic flows.