A couple thoughts.. I remember using a method ( long before using Tapestry ) where you write out a "please wait" message then close the body tag and flush the outputstream, but keep it open. The browser displays the page but when you are ready you write out a new body tag with the actual content and an onLoad that clears the previous content (or something like that). The problem with this is that eventually the browser times out anyway.. so anything more than a few minutes is no good.
Alternatively, we could write something that could be used application wide where if any request takes too long to respond a quick "please wait, experiencing heavy load" message comes up that has a JS refresh every 5 secs or so that checks with a Tapestry "DelayedPage" service or something of that nature. If when the original request went too long, an id would be assigned to the request which would be used when the request eventually completes (to add to some list of delayed responses waiting to be picked up).. and the "Please Wait" page would use this id when checking if it's job is picked up. Not to go crazy here.. but you could further expand this to make the "Please Wait" page have a "Email me when this task is complete" for really long jobs. Maybe this would take the form of a "PossiblyDelayedActionLink".. that functions just like an ActionLink... Luke Galea Software Development BlueCat Networks 905-762-5225 -----Original Message----- From: Joseph Panico [mailto:[EMAIL PROTECTED]] Sent: November 21, 2002 3:21 PM To: [EMAIL PROTECTED] Subject: [Tapestry-developer] long running response component? What are Tapestry people using to provide users with feedback during long-running requests? By "long-running" request, I mean the user hits a button and has to wait a minute or two (or 20 :)) before the final result page is returned because the task triggered by the button push is just so time consuming. Basic UI design dictates trying to provide feedback during this processing "lull". Have people come up with any components to handle providing feedback for this scenario? If not components, then what kind of techniques? Http meta-refresh? Javascript hackery? Joseph Panico [EMAIL PROTECTED] _________________________________________________________________ MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*. http://join.msn.com/?page=features/virus ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
