Re: sftp_async_read_begin + uint32_t

[Andreas Schneider <asn@xxxxxxxxxxxxxx>]

On Tuesday, 14 November 2017 12:08:06 CET Nikos Mavrogiannopoulos wrote:
> Hi,

Hi,

>  While adding support of libssh to curl, I stumbled on the
> sftp_async_read_begin and sftp_async_read APIs. Both accept file
> size as uint32_t instead of size_t. In SCP or the other SFTP APIs,
> there is no such limitation. Is that limitation intentional?

this shouldn't really be a problem as you should read in junks. The sizes of 
those chunks should be 16k, 32k, ... Using chunks of more than 4GB doesn't 
really make sense.

So you're saying curl uses chunks bigger than 4GB?

> Would it make sense to try to work around that limitation in curl, or
> provide a patch for libssh to handle longer than 32-bit sizes?

The only thing which would make sense would be a completely new async API for 
sftp!


	Andreas


-- 
Andreas Schneider                   GPG-ID: CC014E3D
www.cryptomilk.org                asn@xxxxxxxxxxxxxx