Is this a bug or a feature, that curlftpfs on read first reads the whole file in to memory and only then gives access to it?
Found this trying to copy huge file (~600Mb) from ftp server
Should it be better to use curl_multi instead of curl_easy and access only needed part of the file?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It is a TODO to implement the loading of the file as needed. It will probably be in the next version. I still don't know if I'll use the multi interface or use multiple threads.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
not reading the entire file would be cool. especially when nautilus tries to fetch the beginning of a file for mime type detection/preview rendering. is this already implemented in 0.9.1?
btw, is the CVS up to date? (the configure.ac is still version 0.9)
norbert
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Is this a bug or a feature, that curlftpfs on read first reads the whole file in to memory and only then gives access to it?
Found this trying to copy huge file (~600Mb) from ftp server
Should it be better to use curl_multi instead of curl_easy and access only needed part of the file?
It is a TODO to implement the loading of the file as needed. It will probably be in the next version. I still don't know if I'll use the multi interface or use multiple threads.
not reading the entire file would be cool. especially when nautilus tries to fetch the beginning of a file for mime type detection/preview rendering. is this already implemented in 0.9.1?
btw, is the CVS up to date? (the configure.ac is still version 0.9)
norbert