djm at mindrot.org
Thu Sep 18 17:38:49 EST 2003
On Wed, 2003-09-17 at 14:03, Dan Kaminsky wrote:
> It's a mighty inefficient codepath that literally reads data out of
> order and sends it such; disk seek times are deadly. That being said,
> simply implement a cache that handles out of order transactions and only
> writes to disk complete windows of data.
Given that I know of no sftp server implementations that actually do out
of order replies, I don't think we should complexify our client with
such an algorithm.
Even if some braindead vendor decided to do this, I'd probably not
change our client to 1) keep it simple and 2) punish the fools.
More information about the openssh-unix-dev