Hi,
I'm working with the Webdav Client library -- which, in turn, uses the HttpClient lib -- to transfer large (several hundred MBs) files between servers. The problem I'm having has to do with insistence of HttpClientcode to transfer content data to a local storage (be it a temp file or memory), immediately upon a method's execution. In my case, I don't need to store the content locally, but rather want to pump it to another server. Looking at the code, I see that the reason for this behavior lies with the call to parseResponse() from within executeMethod(). My question is, would it be possible to change the behavior of the code, to, having parsed the headers, leave the content data inside the original input stream, so that, if needed, this stream could be returned to the caller instead of a new one made from a locally cached copy? A new method, let's say, getMethodDataUnprocessed() would simply return this stream, while calling getMethodData() would make a call to parseResponse() first, and then continue with the old behavior. Comments? Regards Dmitry -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
