Hi
> We had a similar problem. We just added a "preparation" step before the > actual download. > > 1. User clicks on "request download" link 2. jQuery sends a request to > servlet and instructs it to prepare the download 3. Meanwhile > the request download link has been changed with Javascript to "preparing > download..." > 4. jQuery periodically asks the servlet if the download is ready or if the > preparation has failed 5. If it is ready, the "preparing > download..." is replaced by "download file" - if it has failed, an error > message would be displayed > > This of course will only work if the client supports Javascript. But even if > it doesn't you can work with HTTP reloads and/or redirects > and using unique IDs to identify your client and their download. Yes, we thought about that. However it still leaves the problem of a lot of storage on the server that is used for no reason and increasing the time to download the backup.. Regards, Steffen
smime.p7s
Description: S/MIME cryptographic signature
