>> We're talking about multiple copy operations. The first one copies 230 >> files (approx. 40mb) and the second one copies about 2200 files >> (195mb). Most files are under 400kb a piece. > > Time how long it takes you to manually copy that amount of data. Tried the flush() calls in between different parts of the request, doesn't help :-( Although I don't get why you'd want me to time the copying, I did. In fact, I timed all operations... Deleting the old files takes about 3 seconds, copying the new data takes about 20 sec, database requests and generating XML takes another 10 seconds. All in all, the complete operation takes < 35sec, which should be fast enough to prevent the browser or server from timing out..
Well, if it took a minute to copy the data, then your disks need tuning or something and nothing you do in php would affect this.
BTW, would a timeout explain why the browser wants to repost the request when I trie to view the source-code of the blank-page?
I think that's a firefox thing.. does the same thing happen in IE?
> If you're trying to do all of this in one step I think you're out of > luck and you might need to break up the processes. What do you mean by breaking up the processes? Put them in different requests, so that one request calls another one?
have a "publish site" button that opens a small popup window. step 1 - prepare the new environment (make dirs, whatever) (refresh automatically) step 2 - copy the files (refresh automatically) step 3 - create the xml (refresh automatically) step 4 ... use a session variable for example to work out where you are up to and what to do next. -- Postgresql & php tutorials http://www.designmagick.com/ -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
