2012/4/27 Christopher Schultz <ch...@christopherschultz.net>: > > In the browser (Firefox 11.0 and 12.0 in our case), we can see the > throbber work for a good 10-20 seconds *after* the upload has failed > - -- our code has stopped running -- apparently waiting for something. >
Just several notes 1. See config/context.html -> swallowAbortedUploads 2. The "throbber work" is client-side issue. If it wastes his own resources that is his own problem. I would be more worried what is the load on the server and on the network when this happens. (That would need some diagnosing work). Just for starting - the status page in the Manager webapp shows the current request processing threads and their status. 3. In GMail there is such a feature that when I make an attachment I do not need to navigate to another page. The file is uploaded asynchronously. I wonder how it is done (Flash?) and whether you can have better error handling at client side if you use similar approach. E.g. JavaScript detects that upload failed and then makes additional HTTP request to get error details from the server. Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
