Differences
This shows you the differences between the selected revisions of the page.
| 2017-02-02 | 2023-02-10 (current) | ||
| transferring explicit anchor (martin) | 6.0 Bug 195 Ongoing delete operation can be moved to background queue + replaced some "transfers" with "operations", but overal, still keeping focus on transfers, for simplicity (martin) | ||
| Line 1: | Line 1: | ||
| - | ====== Transfer Queue / Background Transfers ====== | + | ====== Transfer Queue / Background Operations ====== |
| - | By default WinSCP transfers files on foreground. This way it can use one connection to the server only all the time, however during the transfer you cannot use WinSCP for any other task. Alternative way is to use background transfers. | + | By default WinSCP performs files transfers and other operations on the foreground. This way it can use one connection to the server only all the time, however during the operation you cannot use WinSCP for any other task. Alternative way is to perform the operations on the background. |
| ===== [[transferring]] Transferring Files on Background ===== | ===== [[transferring]] Transferring Files on Background ===== | ||
| - | To instruct WinSCP to perform the transfer on background, check //Transfer on background (add to transfer queue)// on [[ui_copy|transfer options dialog]] before the transfer. If you do not use the dialog or want to transfer file on background by default, check //[[ui_pref_background#background_transfers|Transfer on background by default]]// on //Background page// of Preferences dialog. You can also move ongoing foreground transfer to background using //[[ui_progress#controlling|Move to Background]]// command. Also, you can drop files onto [[ui_queue|background transfers queue list]] to transfer them on background. | + | To instruct WinSCP to perform the transfer on background, check //Transfer on background (add to transfer queue)// on [[ui_copy|transfer options dialog]] before the transfer. If you do not use the dialog or want to transfer file on background by default, check //[[ui_pref_background#background_transfers|Transfer on background by default]]// on //Background page// of Preferences dialog. Also, you can drop files onto [[ui_queue|background transfers queue list]] to transfer them on background. |
| - | Once you instruct WinSCP to perform the transfer on background, the transfer is added at the end of transfer queue (visualized by [[ui_queue|background transfers queue list]]). | + | You can also move ongoing foreground transfer or delete operation to the background using //[[ui_progress#controlling|Move to Background]]// command. For the delete operation, this is only way to perform it on the background. |
| - | WinSCP by default performs at most two background transfers at once. If you schedule more transfers, those will wait in the queue until some previous transfer is finished. For each background transfer WinSCP opens separate connection to the server using the same session option as used for the main session. Once the transfer finishes the connection is kept on background and reused for future transfers. | + | Once you instruct WinSCP to perform the operation on background, the operation is added at the end of the queue (visualized by [[ui_queue|background queue list]]). |
| - | You can change number of simultaneous transfers on //[[ui_pref_background|Background page]]// of Preferences dialog. You can also allow WinSCP to process [[ui_queue#manage|particular transfer despite the limits]]. | + | WinSCP by default performs at most two background operations at once. If you schedule more operations, those will wait in the queue until some previous operation is finished. For each background operation WinSCP opens separate connection to the server using the same session option as used for the main session. Once the operation finishes the connection is kept on background and reused for future operations. |
| + | |||
| + | You can change number of simultaneous operations on //[[ui_pref_background|Background page]]// of Preferences dialog. You can also allow WinSCP to process [[ui_queue#manage|particular operation despite the limits]]. | ||
| Alternatively you can instruct WinSCP not to [[ui_pref_background#background_transfers|process the queue by default]], but wait instead, until you [[ui_queue#manage|explicitly ask for it]]. | Alternatively you can instruct WinSCP not to [[ui_pref_background#background_transfers|process the queue by default]], but wait instead, until you [[ui_queue#manage|explicitly ask for it]]. | ||
| - | Once the background transfer finishes, the target directory is reloaded (still on background) and content of the respective [[ui_file_panel|file panel]] is refreshed. | + | Once the background operation finishes, the target directory is reloaded (still on the background) and content of the respective [[ui_file_panel|file panel]] is refreshed. |
| ===== Controlling the Queue ===== | ===== Controlling the Queue ===== | ||
| - | Once you have your transfers scheduled, you can use [[ui_queue|queue list]] to manage them. | + | Once you have your operations scheduled, you can use [[ui_queue|queue list]] to manage them. |