> Why should this be a problem? Over the network,
> maximum segments you get are (after removing
> framing/chunking overhead) probably that 1440 bytes in
> size, and httpclient is then returning you as much
> data as it can efficiently give at any given time.
> You just keep on reading all the data, piece by piece.
> That's how streams work; they present an abstraction
> over what may be (and often is) packet-based transport
> channel.
some peaces are about 55 KB size, and first read is 75 KB. so why are all
other about 1.4 KB?
and after - saving inputStream into FileOutputStream load CPU for great
number... this time it is really a problem... tested with different buffer
sized, and with greater buffer size have lower CPU load.
P.S.: speed of downloading about 5 MB/s...
--
best regards,
Paranoid
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
