Yes, we just discussed that. If this code is helpful for general cases, we would like to contribute that. However, the jsse stuff still need times to do... And a good news for http client is that jdk1.4 will fully implement RFC2616(http1.1). I attended a networking session of javaone. The speaker, from sun, made this statement. So, if this implementation will be available soon, it will be better to use that in the httpsender.
-chen > -----Original Message----- > From: Ng, Charles [mailto:[EMAIL PROTECTED]] > Sent: Thursday, April 04, 2002 2:10 PM > To: '[EMAIL PROTECTED]' > Cc: Boyd, Garth > Subject: RE: HTTPSender > > > Hi Chen. > > I think that will be very helpful. Specifically, the ability to fully > configure JSSE is really what I want. > > Do you plan to commit this code? > > Thanks, > Charles > > -----Original Message----- > From: CHEN,SHIH-CHANG (HP-NewJersey,ex2) > [mailto:[EMAIL PROTECTED]] > Sent: Thursday, April 04, 2002 2:03 PM > To: '[EMAIL PROTECTED]' > Cc: '[EMAIL PROTECTED]' > Subject: RE: HTTPSender > > > 1. I have tired to modify the HTTPSender to use the httpclient > in apache common project. The purpose is as you said to support > Keep-alive and chunking transfer-encoding. However, httpclient > does not fit my need very well and I found it have problems > when using http proxy. So, is the httpclient lib mature enough > to be used in Soap-client ? > > 2. Right now, I already have a working modified HTTPSender that > support Keep-alive and chunking transfer-encoding. The > performance improvement is not significant but visible, around > 10% ~ 15% using localhost tomcat. > > 3. For the HTTPSender, I also plan to make all the JSSE > properties configurable. Therefore user can specify the security > properties programmatically or by config rather than using defaults. > > Let me know if my modified HTTPSender is valuable for you ... > > -chen > > > -----Original Message----- > > From: Ng, Charles [mailto:[EMAIL PROTECTED]] > > Sent: Thursday, April 04, 2002 12:35 PM > > To: '[EMAIL PROTECTED]' > > Subject: HTTPSender > > > > > > Hi. > > > > Are there any plans to use the Jakarta Common's HTTP client > > to implement > > HTTPSender? There are features in HTTP 1.1 that are useful > > (e.g. Keep-alive > > and chunking). Also, there will be less code to maintain. > > > > Charles > > > > This message may contain privileged and/or confidential > > information. If you > > have received this e-mail in error or are not the intended > > recipient, you > > may not use, copy, disseminate or distribute it; do not open any > > attachments, delete it immediately from your system and > > notify the sender > > promptly by e-mail that you have done so. Thank you. > > > > This message may contain privileged and/or confidential > information. If you > have received this e-mail in error or are not the intended > recipient, you > may not use, copy, disseminate or distribute it; do not open any > attachments, delete it immediately from your system and > notify the sender > promptly by e-mail that you have done so. Thank you. >
