Thanks for your fast help...
Adding a "extra" header will work for me. The context I am working in
is a P2P-based solution
where peers transfer data from one node to another using http (Jetty
as Server, HttpClient as client).
Peers can find themselves automatically using DNS-SD (JmDNS) - only
one the local link. So far I can`t
be involved by range-caching proxies as Roland Weber mentioned.
I only have one question left. The code Christophe Kualasoft has
provided, starts receiving from a given
offset up to the end of the requested object (RFC 2616 14.35). If I
want to stop receiving before the end
of that object, is it acceptable to close the corresponding
InputStream? Or is it "nicer" to specify
a content range like 'Content-Range: bytes 500-999/1234' as defined
in RFC 2616 14.16.
My Problem is, that i am not sure, how much I want to read...
Bye, Peter
