You may just need a flush() call after the Starting UNZIP.
http://php.net/flush
PHP (Apache, actually) sends data to the browser when there's enough to
send, not right away.
--
WARNING [EMAIL PROTECTED] address is an endangered species -- Use
[EMAIL PROTECTED]
Wanna help me out? Like Music? Buy a CD: http://l-i-e.com/artists.htm
Volunteer a little time: http://chatmusic.com/volunteer.htm
----- Original Message -----
From: Ray Clouse <[EMAIL PROTECTED]>
Newsgroups: php.general
To: <[EMAIL PROTECTED]>
Cc: php <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Tuesday, August 21, 2001 10:10 AM
Subject: Re: [PHP] Need "Working..." pop up dialog (repost)
> It's due to space restrictions on the server. We have 300GB available
> on the server, but the compressed data takes up 200GB, and we're adding
> new data (several GB) every month or so.
>
> So we need to keep as much compressed as possible, but we have to
> uncompress the data for the webpages to use it. The PHP webpages on the
> server use the uncompressed data to generate plots. The data is never
> sent to the user, just the plots.
>
> The main problem I'm having is with page resolution. If I say:
>
> print("<SCRIPT>jsPopupWindow('Starting UNZIP');</SCRIPT>\n");
>
> $gunzipcmdline = "gunzip /PATHTO/MYDATA";
> $result = exec("$gunzipcmdline", $execout, $execretval);
>
> print("<SCRIPT>jsPopupWindow('Finished UNZIP');</SCRIPT>\n");
>
> the 'Starting UNZIP' popup appears at the same time as the 'Finished
> UNZIP' one. The page hasn't resolved until after the gunzip is done, so
> it doesn't execute the Javascript the way I want it to. I've tried
> popping up a window, getting the handle, passing the handle to the
> gunzip code, then closing the handle when the gunzip is done, but that
> hasn't worked either.
>
> Justin French wrote:
>
> >Ray Clouse wrote:
> >
> >>When the user clicks on a link that has to gunzip a very large file, I
> >>want a popup to say "Working..." while the file is uncompressing.
> >>Then, when the file is uncompressed, I want the "Working..." popup to
> >>close itself and then the parent window to load a new URL (where it
> >>will use the uncompressed file).
> >>
> >>I've tried doing this with Javascript and window.open(), but I'm having
> >>no luck. Any ideas?
> >>
> >
> >Is the uncompressing taking place on the server? or on the local (user)
> >machine? Sounds like it's on the server.
> >
> >The problem is, you have no *real* way of knowing how long the de-comp
> >will take (due to other factors, like server/client load, etc etc), so
> >how do you know when to go from "working" to "done".
> >
> >
> >So, i'm trying to figure out WHY you're uncompressing a file on the
> >server that will be used by visitors over http.
> >
> >Seems wrong to me. Increased server load, more programs, more problems,
> >slower server response time, increased user anger, etc etc.
> >
> >
> >Enlighten me as to why, because I may be missing something.
> >
> >
> >Justin French
> >
>
> --
> -------------------------------------------------------------------------
> Ray Clouse | Don't fear the penguins.
> Engineer Scientist/Specialist |
> Boeing Expendable Launch Vehicles | Ray.Clouse AT boeing.com
> Huntington Beach, CA | clouse AT rayclouse.org
>
>
>
>
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
