xml-soap-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Narayanan Seshadri <Naraya...@Yodlee.com>
Subject RE: Soap4J and HTTP 1.1 Keep-Alive/Persistent support
Date Mon, 11 Jun 2001 20:26:31 GMT
> -----Original Message-----
> From: Sanjiva Weerawarana [mailto:sanjiva@watson.ibm.com]
> Sent: June 10, 2001 10:25 PM
> To: soap-dev@xml.apache.org
> Subject: Re: Soap4J and HTTP 1.1 Keep-Alive/Persistent support
> 
 
> I have to believe that keep-alive would make a big perf difference
> in repeated calls over long networks scenarios.
> 
> BTW, what does this have to do with http chunking?

Using HTTP 1.1 and Keep-Alive returns the response using the
Transport-encoding: chunked

This means, that the body of the response will include the content-length.
This results in xml parser failure, through SOAP4J.

-Narayanan
> 
> Sanjiva.
> 
> ----- Original Message -----
> From: "Scott Nichol" <snichol@computer.org>
> To: <soap-dev@xml.apache.org>
> Sent: Friday, June 08, 2001 9:25 AM
> Subject: Re: Soap4J and HTTP 1.1 Keep-Alive/Persistent support
> 
> 
> > 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" <Narayanan@Yodlee.com>
> > To: <soap-dev@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
> 

Mime
View raw message