In our case, it was just a matter of checking validation, setting a cookie, then Meta-refreshing to another page. Didn't have a need for CFFLUSH.
-----Original Message----- From: Brook Davies [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 1:27 PM To: [EMAIL PROTECTED] Subject: RE: Progress indication and FB Do you use this in conjunction with CFFLUSH? If not, how? At 12:48 PM 20/06/02 -0500, you wrote: >I've actually implemented this GIF solution on a fairly large site that it >used by a network of dealers all the time. I use it while the app checks for >user validation. None are the wiser. It's a simple green "progress" gif... >with the words "Authorizing Access Code". Sounds all high-tech n' stuff. :D >Cracked me and the other developer up but it works like a charm. > >Scott > >-----Original Message----- >From: Alan McCollough [mailto:[EMAIL PROTECTED]] >Sent: Thursday, June 20, 2002 12:10 PM >To: '[EMAIL PROTECTED]' >Subject: RE: Progress indication and FB > > >Rave and think, buddy, go for it. Until Nat the topic cop catches up with >ya, that is. Heh. > >Now let me ask y'all... From a developer's side, we all know that the only >purpose for a progress bar is to keep the end user from going nuts and >clicking "Submit" 20 times in a row out of impatience. It doesn't make >anything run faster, and in fact, if it's doing ANYTHING server-side, >actually makes things take longer. > >Is it -really- beneficial to create a super-accurate progress bar that is >consuming server time just to let the user know "Not Yet"? I'm not saying >the users are cockroaches or anything, but I really think if you know your >process takes X seconds under load, then displaying an animated GIF that is >(X * 1.25) seconds long to complete will probably do the trick. > >Let's think it out. Three possibilities exist: > >1.) The process completes before the GIF runs out = User is estatic! >2.) The process completes when the GIF runs out = User is satisfied. >3.) The GIF runs out before the process completes = User will grow >impatient, and probably reclick madly > >By increasing the amount of time the GIF runs, you increase the odds of 1.) >occuring and decrease the odds that 3.) occurs. All without spending a >single CPU cycle on the server, or tossing so much as a byte of bandwith to >the skies. > >I'm trying to think of a single "big boy" site I've used, such as a stock >trading site, that has anything other than a "This may take a minute, do not >double submit!" notice. Can't think of one. > >Sorry if that sounds fbcommunity-ish, folks. > > > -----Original Message----- > > From: Lee Foster [SMTP:[EMAIL PROTECTED]] > > Sent: Thursday, June 20, 2002 6:37 AM > > To: [EMAIL PROTECTED] > > Subject: RE: Progress indication and FB > > > > I've been thinking about this for while for a new software package that > > I've > > been talking about with Steve Nelson, Lee Borkman and others about. I > > still > > think a flash version is the best answer. Don't get me wrong. If someone > > is great in Java I'm sure they can write up a nice version too. But in my > > case my Java is a bit ghostly in the black hole I call a brain. So I > > would > > use Flash. > > > > My question would be in Fusebox or anything for that matter. How would I > > update the application status without reloading the page and still do the > > actions. Currently the best guess I have is to open up a very small > > window > > (25 x 25) and have JavaScript somehow send the updates to the main window > > that has the Flash movie in it. When all of the actions are complete the > > small windows would send a done indication to the main screen and just > > close. > > > > Sorry about the raving and thinking out loud, > > > > > > Lee Foster > > (e)consultant, Web developer, Web Architect > > [EMAIL PROTECTED] > > 615-834-1876 > > http://www.l3enterprises.com > > Nashville, TN > > -----Original Message----- > > From: David Huyck [mailto:[EMAIL PROTECTED]] > > Sent: Thursday, June 20, 2002 8:53 AM > > To: [EMAIL PROTECTED] > > Subject: Re: Progress indication and FB > > > > The method I like is to have your form submit to a page that only does two > > things: > > 1) it displays a message stating that the application is working-- with an > > animation of some sort (think expedia or orbitz or something when it is > > searching the database for flights-- takes 30+ seconds everytime) > > 2) it resubmits your data to the "real" destination where your fuseaction > > can > > process the data appropriately and take its time... > > > > HTH, > > David Huyck > > [EMAIL PROTECTED] > > > > ----- Original Message ----- > > From: <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Wednesday, June 19, 2002 5:04 PM > > Subject: Progress indication and FB > > > > > > | So I have a fuseaction that is mega process intensive. (I know I need > > to > > | tune it) > > | Anyhow. > > | Anyone have any good ways to give the user some sort of indication that > > the > > | application is working so they do not click again? > > | > > | -Drew Harris > > | > > | > > > > > > > ==^================================================================ This email was sent to: [email protected] EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^================================================================
