Do you have the ability to have multiple client-server connections open? You
could have a second channel to the server that can communicate the status to
the client and when/if there is a problem indicate through that status channel
that the download has been truncated. Not the greatest idea bec
Am 03.06.2016 um 15:51 schrieb Steffen Heil (Mailinglisten):
> NO. We want to stream the results to the client... It usually is
> several times bigger than the memory at hand.
I can think of three options right now:
* Know the content-length upfront (which you don't) - with that clients
could det
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
"pre
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Steffen,
On 5/29/16 2:08 PM, Steffen Heil (Mailinglisten) wrote:
> I am streaming a huge file from a servlet to the browser. It can
> easily be multiple gigabytes.
>
> Currently the data is prepared on the server, stored in a file and
> then sent t
