On 7/12/07 10:22 PM, "Brent Baisley" <[EMAIL PROTECTED]> wrote:
> I think you can rely on Javascript being present and enabled, with the all the
> web 2.0 stuff out there it just about has to be.
>
> When I needed to run something long, I've run it in the background using the
> exec command. If y
I think you can rely on Javascript being present and enabled, with
the all the web 2.0 stuff out there it just about has to be.
When I needed to run something long, I've run it in the background
using the exec command. If you have command line php enabled, this
could be just another php scr
I did something like what you see on orbitz.
Check it out..
http://tconeill.com/examples/pixelcrunch/
On 7/10/07, Tim Lieberman <[EMAIL PROTECTED]> wrote:
Never really thought about it.
If your backend processes is asynchronous (or if you make it so) you
could have your "progress" script j
Never really thought about it.
If your backend processes is asynchronous (or if you make it so) you
could have your "progress" script just meta refresh until the back-end
has a result, and then on the next refresh, 302 out of there.
Cliff Hirsch wrote:
For long and indeterminate page processi
For long and indeterminate page processing, like connecting with a credit
card payment gateway or calculating pi to thousands of significant digits,
what is your preferred method for displaying ³please wait²?
I see two techniques:
1. Use Javascript upon form submission to display the ³please wait²
