Abstract: TCP data packets are transferred from a plurality of server nodes to a client node, wherein the proxy node captures all packets of the TCP flows, buffers the captured packets in a TCP stack and updates an active TCP flow list in a subscriber record representing the client node. A current proxy scheduling capacity from a current maximum amount of data allowed concurrently in transmission in one more TCP flows to the client node is estimated. When a triggering event is received, a packet retrieved from the TCP stack is scheduled in accordance with the estimated current proxy scheduling capacity and order given by the active flow list. The scheduled packet is transmitted and the active flow list is updated, whereupon scheduling a TCP flow for transmission is repeated until the current proxy scheduling capacity has been reached or there are no TCP flows in the active flow list.

Abstract: TCP data packets are transferred from a plurality of server nodes to a client node, wherein the proxy node captures all packets of the TCP flows, buffers the captured packets in a TCP stack and updates an active TCP flow list in a subscriber record representing the client node. A current proxy scheduling capacity from a current maximum amount of data allowed concurrently in transmission in one or more TCP flows to the client node is estimated. When a triggering event is received, a packet retrieved from the TCP stack is scheduled in accordance with the estimated current proxy scheduling capacity and order given by the active flow list. The scheduled packet is transmitted and the active flow list is updated, whereupon the step of scheduling a TCP flow for transmission is repeated until the current proxy scheduling capacity has been reached or there are no TCP flows in the active flow list.