TeamAmaze / TeamAmaze/AmazeFileManager
Optimize CopyService/GenericCopyUtil
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 6.4k
- Forks
- 1.7k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 1
Description
Is your feature request related to a problem? Please describe.
Slow moving/copying multiple files/folder structures, especially when source file is on remote server, be it SMB, SSH of FTP(S)
Describe the solution you'd like
CopyService/GenericCopyUtil should be able to consolidate list of file operations before starting, so that connection sessions (mostly used with SSH/FTP) can be reused for transferring multiple files instead of rapidly setup/teardown connections
Describe alternatives you've considered
N/A
Additional context
#3888
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading CopyService and GenericCopyUtil, then review the related context in issue #3888. Trace how multiple-file operations are currently created for SMB, SSH, and FTP(S) sources; done means consolidating operations so reusable connection sessions transfer multiple files without repeated setup and teardown.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- mobile, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100