Re: Soap4J and HTTP 1.1 Keep-Alive/Persistent support

[Rob Jellinghaus <ro...@unrealities.com>]

Do we have any plans to support this?  Currently our HTTPDispatchHandler
(which I am going to rename HTTPSender) also opens a new socket per
request....

Cheers,
Rob


>Return-Path: soap-dev-return-6301-robj=unrealities.com@xml.apache.org
>Mailing-List: contact soap-dev-help@xml.apache.org; run by ezmlm
>Reply-To: soap-dev@xml.apache.org
>list-help: <ma...@xml.apache.org>
>list-unsubscribe: <ma...@xml.apache.org>
>list-post: <ma...@xml.apache.org>
>Delivered-To: mailing list soap-dev@xml.apache.org
>From: "Scott Nichol" <sn...@computer.org>
>To: <so...@xml.apache.org>
>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: h31.sny.collab.net 1.6.2 0/1000/N
>X-Rcpt-To: robj@unrealities.com
>
>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 (http://xml.apache.org/axis/), which will replace Apache
>SOAP.
>
>Scott
>
>----- Original Message -----
>From: "Narayanan Seshadri" <Na...@Yodlee.com>
>To: <so...@xml.apache.org>
>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
>content-length
>> as part of the body of the message. Because of this extra content-length
>in
>> 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
>
>
>