To: Commons HttpClient Project
Subject: Re: upload large files- Filepart
Oleg Kalnichevski wrote:
Siddhartha,
I believe the solution to this problem is trivial. All it takes is
checking for availability of a response from the target server prior to
sending each consecutive chunk of request
Kalnichevski, Oleg wrote:
Can you give me more details as to why you think this may cause problems with HTTP pipelining?
It won't if done right :-) You just need to make sure that you are
monitoring the response corresponding to the request and not any other
response from previously pipelined
This problem seems like it is the perfect candidate for the
ExpectContinueMethod.setUseExpectHeader() function. Isn't this exactly
the scenario for which this header was intended?
-Eric
Oleg Kalnichevski wrote:
Siddhartha,
I believe the solution to this problem is trivial. All it takes is
that is correct unfortunately I have had the
privilege to work on a webserver which is supposed
to be 1.1 compliant..
I am trying hard to get them to support the 100-expect
continue at the same time I want to see if I can get a
work around.. and hence the mails!!
--- Kalnichevski, Oleg
[EMAIL
Siddhartha,
I believe the solution to this problem is trivial. All it takes is
checking for availability of a response from the target server prior to
sending each consecutive chunk of request body. A premature response
from the target server detected before the request body has been
transmitted
from looking at the filepart code seems that this part
would be creating a problem which makes the code not
recoverable from the server closing the connection
when authentication fails...
Filepart.java for httpclient
sendData(){
create a new byte array of size 4K
while thereis stuff to be read
