axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rob Jellinghaus <>
Subject Re: Soap4J and HTTP 1.1 Keep-Alive/Persistent support
Date Mon, 11 Jun 2001 01:02:19 GMT
Do we have any plans to support this?  Currently our HTTPDispatchHandler
(which I am going to rename HTTPSender) also opens a new socket per


>Mailing-List: contact; run by ezmlm
>list-help: <>
>list-unsubscribe: <>
>list-post: <>
>Delivered-To: mailing list
>From: "Scott Nichol" <>
>To: <>
>Subject: Re: Soap4J and HTTP 1.1 Keep-Alive/Persistent support
>Date: Fri, 8 Jun 2001 09:25:14 -0400
>X-MSMail-Priority: Normal
>X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
>X-Spam-Rating: 1.6.2 0/1000/N
>More directly related to the subject of this message, Apache SOAP opens a
>new connection for each request.  There is no provision for maintaining a
>connection between calls.  As to whether it will be supported, I suggest you
>check out Axis (, which will replace Apache
>----- Original Message -----
>From: "Narayanan Seshadri" <>
>To: <>
>Sent: Thursday, June 07, 2001 6:36 PM
>Subject: Soap4J and HTTP 1.1 Keep-Alive/Persistent support
>> Hi,
>> If this topic is already discussed, please point me the message thread.
>> I am trying to use the SOAP4J and take advantage of HTTP 1.1 's keep-alive
>> functionality. I am interested in doing this to avoid creating a socket
>> every time and use the same connection to make multiple requests one after
>> the other.
>> I have tried to use the latest SOAP implementation and found that the HTTP
>> response header has Transfer-Encoding: chunked which adds the
>> as part of the body of the message. Because of this extra content-length
>> the body of the message, the parser throws exception.
>> Is there  a plan to handle this chunked encoding and extract the message
>> appropriately?
>> Thanks
>> -Narayanan

View raw message