Watch a server 'hot' folder and automatically download any new content

[David Sutherland]

I know there are probably lots of other features requested but this feature would make FZ stand out more.

The goal is to keep a folder on a server and the folder on my client machine in sync, in so far as to download new content that shows up. I want the client machine running FZ to 'regularly' poll the server and compare the files on the server with those of the local machine. (The polling time ideally can be set in local preferences.)

When a new file is added FZ should start downloading. The mechanism for detecting what is new could be to compare the folders contents by filename, size and possibly creation date.

While this is a feature MOST people won't need there is probably a smaller group who can really use this and it would make FileZilla outshine the other clients.

Thanks for considering this.

[Tim Kosse]

FileZilla is not intended to be used for automated tasks. You want to use a commandline client for such tasks.

[David Sutherland]

re: "FileZilla is not intended to be used for automated tasks. You want to use a commandline client for such tasks."

Actually, no I do not wish to use a command line utility for automated tasks.

Your logic fails and is plainly arbitrary.

Might I ask why Filezilla, a great ftp client, with GUI features, cannot be expected to handle a monitor folder queue? There seems nothing arbitrarily command-line oriented about it. Actually, come to think of it, it sounds like something a cmd-line tool would do particularly poorly compared to a windows-based client.

There are still very few ftp tools with a watch folder feature. I still believe filezilla would add a very powerful tool to a small but very active group of ftp users.

Winscp as a similar feature but will force upstream syncing. Perhaps they will consider adding a "do not upload feature" before filezilla might add a feature that is clearly 'too command line oriented' (???)

Still appreciate the code, but am at a loss as to why this feature would be rejected out of hand.

[Tim Kosse]

The right tool for the right task.

To watch a directory for changes and automatically transfer changed files you'd use a commandline client called from a cron job.

Actually, come to think of it, it sounds like something a cmd-line tool would do particularly poorly compared to a windows-based client.

How do you come to that conclusion? Synchronization logic has nothing to do with GUI stuff.

[David Sutherland]

FTP is a command line tool, or started out as one.

If you can't see how queue pool lists make more sense in multiple panes vs. a single line interface on a command line I don't think it's because it doesn't make sense or work the best for users, but it sounds like it's because you've already decided what tools you want to write.

These decisions are arbitrary. The simple fact that a user who works in a GUI environment, who prefers GUI environments is requesting the tool should be a valid enough to prove that watch folder functionality is needed in a GUI environment and it's the right environment and the right tool.

Based on the logic your providing, "The right tool for the right task." I don't see why you should do any work on FileZilla -- command line tools are always the right tool.

Look, I don't want to argue -- you've got apparently a limited vision for functionality that I don't share. You and others working on FileZilla have created an incredibly useful tool. I don't want you to feel that it's unappreciated. If you vision is narrower fine, but just be honest about it and say certain features just require too much work for what it's worth in your perspective. I don't like hearing what I consider totally illogical arguments for why things shouldn't be done though. I've explained I think you're arbitrary in you determination that certain functionality is GUI-worthy and other functionality is not-GUI-worthy and you disagree and have some other way of seeing it. The last thing I want is you guys to feel unappreciated for your work on free software so I don't want to push it.

Please continual to develop, and if you can see it in your own way, please consider pushing the envelope of what "should" and "should not" be features in your code.

(Not everyone knows how to run a cron job to check folder every 5 minutes under windows -- I don't. If I need to download cygwin and figure it out, I will, but then I wonder, why did I, or anyone ever need FileZilla if the answer is to use command-line tools. I also would like to see real-time MD5 hash generation as an option within Filezilla -- which is actually tricky due to resume functionality. I don't think I'd suggest this as a optional feature because, again -- it's something, that although it might take longer to post-compute, is something that I can tough-it through via a command line tool.)

[Tim Kosse]

These decisions are arbitrary. The simple fact that a user who
works in a GUI environment, who prefers GUI environments is
requesting the tool should be a valid enough to prove that watch
folder functionality is needed in a GUI environment and it's the
right environment and the right tool.

There is a difference between a tool that automatically watches some directory and automatically downloads changes and a tool that would be used to edit the configuration scripts that will call the first tool. First tool commandline, second tool GUI.

Another example is the FileZilla Server service. The service itself has no GUI. Configuration is performed by some other tool.

Based on the logic your providing, "The right tool for the right task."
I don't see why you should do any work on FileZilla -- command line
tools are always the right tool.

Your statement is invalid. Disproven by perfect counterexample: Webbrowsers.

Look, I don't want to argue

Yet you do ;)

you've got apparently a limited vision for functionality that I don't share
If you vision is narrower fine, but just be honest about it and say
certain features just require too much work for what it's worth in
your perspective.

Too much work is not the issue. The vision however is. FileZilla is intended to be an interactive GUI FTP client. Adding automated functionality would just add bloat. I am just saying that such functionality would be better suited in some other program dedicated to such task.

I think you're focusing too much on the commandline aspect whereas the real issue behind all this is the fact that automated tasks are out of the scope of FileZilla.

Not everyone knows how to run a cron job to check folder every
5 minutes under windows

Windows has a task scheduler. Essentially just like cron but with a pretty GUI. Under XP open Windows control panel and click on "Scheduled Tasks". On Vista/7 it's there too, probably moved to another place though.

[eternat]

CuteFTP implements this feature and FileZilla should too. I have a server and I want files transported to and from it. That is a job for an FTP client. I want that done without me expressly doing it. That is STILL a job for an FTP client. I feel that the argument here was getting too hung up on the "watching" task and not the file transporting task.