When a server has more than one packet-worth of data to send, there should be an option for the server to indicate to clients that 'more' data is coming. This is a protocol change, so I'm filing this as a bug rather than just making the change. I will eventually do this, though!
A good test case is to use the 'process' setting from (currently) the server-cleanup branch to run /bin/sh for every session (note: you shouldn't do that generally). If you run a long command, like "dmesg", it only sends messages once/second, which is slowwwwwwwwww.
When a server has more than one packet-worth of data to send, there should be an option for the server to indicate to clients that 'more' data is coming. This is a protocol change, so I'm filing this as a bug rather than just making the change. I will eventually do this, though!
A good test case is to use the 'process' setting from (currently) the server-cleanup branch to run /bin/sh for every session (note: you shouldn't do that generally). If you run a long command, like "dmesg", it only sends messages once/second, which is slowwwwwwwwww.