Hello there. first may I say how pleased I am that support for this excelent program has restarted. I have a few suggestions, some will be easy to implement. others not too easy. but thanks for looking.

1) the ability to "lock" a container, once locked the current sites for this container will stay with the container and not be used to transfer, this will allow admins to perform matience on a site without loosing there place if automation starts.

2) A feedback thou the win32::api sendmessage when a transfer has finished. and some infomation about what was sent etc.

3) A tcp port log. like a telnet server. this could be very usefull for scripters to be able to read a live log of what is happening with there automated backups.

4) Ability to right click on a queue. and force start it. this would ignore the available logins set for an ftp and try to transfer anyhow.

5) A way to use the win32::api to also recieve information about stored sites and maybe change items like bookmarks.

I'll leave it there for now. I do have more. but there the main ones I can think of for now.thank you for taking the time to read this. Looking forward to new updates. as allways keep up the good work.

Eff3c7 wrote:Hello there. first may I say how pleased I am that support for this excelent program has restarted. I have a few suggestions, some will be easy to implement. others not too easy. but thanks for looking.

1) the ability to "lock" a container, once locked the current sites for this container will stay with the container and not be used to transfer, this will allow admins to perform matience on a site without loosing there place if automation starts.

2) A feedback thou the win32::api sendmessage when a transfer has finished. and some infomation about what was sent etc.

3) A tcp port log. like a telnet server. this could be very usefull for scripters to be able to read a live log of what is happening with there automated backups.

4) Ability to right click on a queue. and force start it. this would ignore the available logins set for an ftp and try to transfer anyhow.

5) A way to use the win32::api to also recieve information about stored sites and maybe change items like bookmarks.

I'll leave it there for now. I do have more. but there the main ones I can think of for now.thank you for taking the time to read this. Looking forward to new updates. as allways keep up the good work.

Eff3c7

+1I want all those too :D

More support for advanced API functions and scripting in general would be nice. That is one of the reason FTPRush got SO popular in the first place.

For such things, it would be nice to have (at least) read-only access on some kind of bug tracker.I became a huge fan of google code's one, voting on issues could help dev to prioritize and us to follow how it's going.But that's a debate we already had on the old forum, so I won't go into that again since I still don't know if it's the same dev or not...

Skiplist is only based on file being transferred, it can't compare it with existing files, that ain't the right solution.

This option already exists for sfv files but if we don't want to end up with a full screen of specific options, it would be far more flexible to have advanced kind of skips that could take code (.net, js, vb, whatever). That leads me to dream about plugins... :p