Differences
This shows you the differences between the selected revisions of the page.
| 2017-06-02 | 2017-06-02 | ||
| 5.10 Bug 875: Background transfer operations can use multiple connections. (martin) | beta tags (martin) | ||
| Line 14: | Line 14: | ||
| The //Transfer on background by default// checkbox makes WinSCP 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 perform all transfers on background. You can always alter this for particular transfer on [[ui_copy|transfer options dialog]] (if enabled). | ||
| - | //In the latest stable version//, the //Transfer each file individually on background by default// checkbox makes WinSCP en-queue each selected file as separate transfer by default. You can always alter this for particular transfer on [[ui_copy|transfer options dialog]] (if enabled). | + | //In the latest stable version//, the //Transfer each file individually on background by default// checkbox makes WinSCP en-queue each selected file as separate transfer by default. You can always alter this for particular transfer on [[ui_copy|transfer options dialog]] (if enabled). &beta |
| - | //In the latest beta version//, the //Use multiple connections for single transfer// checkbox allows WinSCP to use multiple connections for large queued batch transfers. | + | //In the latest beta version//, the //Use multiple connections for single transfer// checkbox allows WinSCP to use multiple connections for large queued batch transfers. &beta |
| You can check //No confirmations for background transfers// to avoid [[ui_pref_environment#confirmations|overwrite and other confirmations]] for the background transfer. | You can check //No confirmations for background transfers// to avoid [[ui_pref_environment#confirmations|overwrite and other confirmations]] for the background transfer. | ||