asynchronous file copy

[pitonyak]

I cannot comment on any QT specific solutions, but, I have done this sort multiple times. This provided the following advantages:

1. Properly architected, the solution is interruptable. When I used built-in copy methods, they were not. This allowed me to abort a long copy with no problems.
2. If desired, you can easily provide status callbacks. I allowed for callbacks on start and completion of each file. This includes error information if it makes sense.
3. I frequently gather some sort of file fingerprint / hash during the copy. Calculating an MD5 hash in-line did not add any perceivable time to the copy.

I cannot claim that my solution was any faster than any built-in method, but it was not slower either. In other words, it provided advantages with no disadvantages (other than the fact that I needed to write code).

[nikhilqt]

Create a worker thread and put your file copy operations inside it. Create a SIGNAL, SLOT which connect main and the worker thread for any file completion, status. Does it help ?

[doggrant]

Hi nikhilqt,

I certainly thing your suggestion is the way to go, although i'm now thinking the bottleneck in my app may be where i sporn out to an external process to extract some files, before the copy. Doing some tests on my code to confirm this, and then i'll have to do a similar thing with that.

regards,

David

[doggrant]

I realised that the GUI freeze was caused by copying a large number of small files in serial, and not because of copying 1 large file. Therefore after copying each small file, I call QApplication:rocessEvents(), to process any events in the queue. This improved the app's responsiveness.

Now now i'm checking my app for other occurances of this.

cheers for everyones help.

David