We capture and persist this information as well, but are not so concerned about the small percentage that actually don't completely download the file. If this is one of your requirements, then it appears you may have a valid solution.
robert > -----Original Message----- > From: John Moore [mailto:[EMAIL PROTECTED] > Sent: Tuesday, May 11, 2004 1:57 PM > To: Struts Users Mailing List > Subject: Re: Forward after returning content? > > > John Moore wrote: > > > Neat! Yes, this is the way. Thanks Niall and Robert too. > > > I just recalled one of the reasons why I wanted to do it the way I did. > In my original version, where I actually handle the file download, I > record in a database what has been downloaded by whom and when, which I > can do because I can determine whether the download has completed (and > not been cancelled by the user). In the version suggested by Niall and > Robert, this is not so simple, is it? I can only tell that a download > has been requested. I suppose a solution is to still handle the actual > download myself and pass the details of the download as parameters in > the <meta http-equiv="refresh"... section. > > John > > -- > ============================================= > John Moore - Norwich, UK - [EMAIL PROTECTED] > ============================================= > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
