There's some thoughts on the Wiki about implementing "insertials", where the user would see periodic updates in their browser. This involves sending a special multi-part MIME response. On my big, bad list!
----- Original Message ----- From: "Joseph Panico" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, November 21, 2002 3:20 PM 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
