Title: RE: keepalive - multiple choice answer

I wasn't aware of the issues with HttpURLConnection.
Thanks for educating me!

> -----Original Message-----
> From: Steve Loughran [mailto:[EMAIL PROTECTED]]
> Sent: Monday, April 22, 2002 7:15 PM
> To: [EMAIL PROTECTED]
> Subject: Re: keepalive - multiple choice answer
>
> ----- Original Message -----
> From: "Volkmann, Mark" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Monday, April 22, 2002 2:56 PM
> Subject: keepalive - multiple choice answer
>
>
> > I know everybody is busy getting ready for beta 2, but I'd really
> appreciate
> > just a terse answer to this question.
> > Is is possible to get Axis to use HTTP Keep-Alive using the
> latest code?
> > I'm looking at the cost of establishing a new TCP
> connection for each
> > repeated request to the same web service.
> >
> > You can probably pick from the following answers.
>
> I no nothing about the details of this, but
>
> > a) Yes.  If you dig into the code more you'll find it.
> >
> > b) No.  However, we plan to add that real soon,
> >    possibly using HttpURLConnection instead of the Socket class in
> > HttpSender.
>
> That'll be the 'notoriously quirky' HttpUrlConnection will it? Whose
> keep-alive support is so well renowned
> (http://developer.java.sun.com/developer/bugParade/bugs/432598
7.html) that
configuring your server to ignore keep-alive requests from that user agent
is a good thing

>
> c) No.  We don't plan to do that any time soon.
>

I am all for keep-alives, but dont want to go near HttpUrlConnection. Use
that and you get burned fast.



***********************************************************************************
WARNING: All e-mail sent to and from this address will be received or
otherwise recorded by the A.G. Edwards corporate e-mail system and is
subject to archival, monitoring or review by, and/or disclosure to,
someone other than the recipient.
************************************************************************************

Reply via email to