Differences
This shows you the differences between the selected revisions of the page.
| 2011-11-04 | 2011-11-04 | ||
| 4.2.2 bug 97 (martin) | 5.0.3 bug 29 queue processing (martin) | ||
| Line 7: | Line 7: | ||
| The box //Maximal number of transfer at the same time// defines maximal number of background connections that WinSCP can automatically opened at the same time and thus maximal number of parallel background transfers. If you schedule more transfers the others will wait in queue. You can always instruct WinSCP to process [[ui_queue#managing_the_queue|particular transfer despite the limits]]. | The box //Maximal number of transfer at the same time// defines maximal number of background connections that WinSCP can automatically opened at the same time and thus maximal number of parallel background transfers. If you schedule more transfers the others will wait in queue. You can always instruct WinSCP to process [[ui_queue#managing_the_queue|particular transfer despite the limits]]. | ||
| + | |||
| + | When //Enable queue processing by default// is checked, WinSCP starts processing the queue as soon as the first item is added to the list. If it is unchecked, you have to explicitly ask for the queue to be processed using command //Commands > Queue > Process queue// (the command is also available on the queue toolbar). Once the queue is completed, processing is disabled and has to be explicitly enabled again the next time. | ||
| The //Transfer on background by default// checkbox makes WinSCP to perform all transfers on background. You can always alter this for particular transfer on [[ui_copy|transfer options dialog]] (if enabled). | The //Transfer on background by default// checkbox makes WinSCP to perform all transfers on background. You can always alter this for particular transfer on [[ui_copy|transfer options dialog]] (if enabled). | ||