[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

sftp_async_read_begin + uint32_t


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?

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?

regards,
Nikos


Follow-Ups:
Re: sftp_async_read_begin + uint32_tAndreas Schneider <asn@xxxxxxxxxxxxxx>
Archive administrator: postmaster@lists.cynapses.org