~charles/ftpmusync

ebce293714347ff56f2694066ec6adfda5776b3f — Charles Daniels 1 year, 5 months ago 787e785 0.0.1
added roadmap
1 files changed, 25 insertions(+), 0 deletions(-)

M README.md
M README.md => README.md +25 -0
@@ 94,3 94,28 @@ however it has thus far only been tested on the following configurations:

If you've given ftpmusync a try, let me know what systems were used, what
worked, and what didn't.

# Roadmap

* More performant FTP wrapper

	* Currently, every FTP command is executed in a new FTP session, this
	  can be very slow. The FTP wrapper should be modified to allow an
	  existing session to be re-used if one is available.

* GUI

	* A GUI frontend could be added relatively easily, as ftpmusync
	  is already written as a library with a CLI front-end; a GUI could
	  hook the same functions with minimal changes.

* The `net` module could be updated to only import `netifaces` if scanning
  is requested, which would allow ftpmusync to work with only the Python
  standard library in cases where scanning is not required.

* Other methods for determining if a remote file needs updated besides just
  size.

* Ability to synchronize playlist files updated on the device back to the host.

* Automated path-normalization for m3u playlist files.