gvfsd-smb should implement pull mechanism
Submitted by Tomas Bzatek
Assigned to gvf..@..e.bugs
Link to original bug (#592468)
Description
This is a tracker bug, opened as a consequence from bug 588391. As long as libsmbclient has its own mechanism to calculate optimal read block size, we might benefit from it performance-wise. Think at lower CPU usage at least and possibly higher transfer rate.
There were some concerns about GVfsJobPush/GVfsJobPull API as now we have to care about local file errors (file exists, is a directory, symlink etc.). We should probably discuss this before starting porting backends.