#11437 closed Feature request (invalid)
A Mechanism for New Smart FTP Transfer (NSFTP)
Reported by: | Hasan K. | Owned by: | |
---|---|---|---|
Priority: | high | Component: | FileZilla Client |
Keywords: | FTP, FTP Traffic, Bandwidth, NSFTP | Cc: | |
Component version: | Operating system type: | ||
Operating system version: |
Description
All of current technologies that provide File Transfer Protocol re upload whole updated and edited file(s) even if the file changes by a minimum of one byte. This is not sufficient in term of upload time, bandwidth usage and logic. While this can be solved and proposed a solution to the stated scenario. By enabling the FTP client and FTP server to treat only the differences between local files and remote files. Thus for this will amazingly reduce FTP transfer time and speed up the process.
Attachments (1)
Change History (3)
by , 7 years ago
Attachment: | A Mechanism for New Smart FTP Transfer (NSFTP).pdf added |
---|
comment:1 by , 7 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
Quite frankly, that document is bullshit. The only correct part is the preamble before the abstract.
Just a few of the things wrong with the document:
- The name of your contraption can be seen as a violation of a trademark of a certain FTP product vendor
- You clearly did not do your research concerning existing protocols
- No reference to what FTP is
- No reference to what PHP is
- No reference to what JSON is
- What is a byte? 7 bits per byte? 9? 16?
- What is a line?
- What is a column?
- You try to reduce traffic yet use the incredibly verbose JSON
- No specification of the used algorithms
- No analysis of the complexity of the used algorithms
- Not a single word about compatibility and feature negotiation
- Does not deal with conflict resolution in case two users are working on the same file
Could you please forward me the contact information of your department head so that I can lodge a formal complaint?
comment:2 by , 7 years ago
Hi @codesquid,
First of all, I didn't try to cause inconvenience.
My request was with good faith to suggest a way to reduce ftp traffic.
looks I fail to propose a valid method to achieve that.
Yet I don't think you need to offend me.
In addition, that attachment is not an official paper; its just a simple personal contribution and opinion.
Just as a normal and not advanced user; it doesn't look logical for me if I changed a semicoma in a big file to re-upload the whole file...it makes sense but I guess not technically.
Please don't get upset.
take it as a science fiction that someday ftp clients (not a specific brand); but as in technology will be able to find out if the file changes are minor to synchronize the deff only.
My document could be a bullshit, but my goal was to be positive and add something positive.
I hope you got the spirit of my concern.
Thank you so much
Sincerely,
Update:
Usually, when I upload a big bunch of files, I zip them and upload the one zip file to the cPanel by FTP, then from cPanel I unzip and its the same result for uploading files one by one.
I hope (if that is technically possible) this scenario could be implemented in ftp clients.
i.e. client zip files, upload then compatible ftp server unzip.
Thank you
new feature request