; Sent: Monday, June 11, 2001 1:25 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Soap4J and HTTP 1.1 Keep-Alive/Persistent support
>
>
> Actually, Matt was playing around with an impl of keep-alive, but
> I don't think was happy "enough" with it to commit it. I'm
> -Original Message-
> From: Sanjiva Weerawarana [mailto:[EMAIL PROTECTED]]
> Sent: June 10, 2001 10:25 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Soap4J and HTTP 1.1 Keep-Alive/Persistent support
>
> I have to believe that keep-alive would make a big perf differenc
ios.
BTW, what does this have to do with http chunking?
Sanjiva.
- Original Message -
From: "Scott Nichol" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, June 08, 2001 9:25 AM
Subject: Re: Soap4J and HTTP 1.1 Keep-Alive/Persistent support
> More di
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
S
I do not understand how you get chunked encoding at all. Apache SOAP
clients send requests as HTTP/1.0 (cf. HTTPUtils.java). I thought chunked
encoding was a 1.1 feature that a server should not use with a 1.0 client.
Scott
- Original Message -
From: "Narayanan Seshadri" <[EMAIL PROTEC
