On Wed, 9 Jun 2004, Joey Morin wrote:

>    this is because many connection types (like HTTP) employ a scheme
>    whereby acknowledgement packets (ACK) are returned for each packet or
>    group of packets received.
>
>    so, an HTTP server won't send you the next packet in your huge download
>    until it has received an ACK packet for it's last burst.

err, chaps, that is part of the tcp protocol. all tcp connections follow
that behaviour, be it http, ssh, smtp, pop and stuff. udp is a
connectionless protocol and doesnt. udp examples include dns, RADIUS, and
some p2p networks.

>    upload, or bittorent process) leaves little room for small packets
>    generated by keystrokes in an SSH session, so you see some latency.

the soon to be released magic shaper automagically creates a priority
queue for small packets (length < 40bytes payload) to address interactive
usage such as ssh, telnet et al.

Regards,                           /\_/\   "All dogs go to heaven."
dinesh at alphaque dot com                (0 0)    http://www.alphaque.com/
+==========================----oOO--(_)--OOo----==========================+
| for a in past present future; do                                        |
|   for b in clients employers associates relatives neighbours pets; do   |
|   echo "The opinions here in no way reflect the opinions of my $a $b."  |
| done; done                                                              |
+=========================================================================+