axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Glen Daniels" <>
Subject Re: [soapbuilders] Re: kSOAP interop w. WM, Apache, SOAP4R
Date Thu, 02 Aug 2001 12:16:55 GMT
That's why we have a MessageContext; set a transport-independent TIMEOUT
property in the client somewhere and then let anyone who wants to use that
value.  Transport senders like HTTPSender can just set a socket timeout.

On the server, it's a little more challenging, I think.  It would be nice if
there was a way to timeout when user-level service code hangs, but for that
you do need threads.  App-servers might do some of this for us, but we could
still use an architecture that lets us do it standalone.


----- Original Message -----
From: "Doug Davis" <>
To: <>
Sent: Thursday, August 02, 2001 7:03 AM
Subject: Re: [soapbuilders] Re: kSOAP interop w. WM, Apache, SOAP4R

> Socket timeouts are definitely an option - one problem with this is that
> would require it to be done at the transport level.  So each transport
> would be responsible for handling it.  It would be nice if we could find a
> way to do it in the Axis engine itself that way it could be transport
> independent.
> -Dug
> Sam Ruby/Raleigh/IBM@IBMUS on 08/02/2001 06:51:40 AM
> Please respond to
> To:
> cc:
> Subject:  Re: [soapbuilders] Re: kSOAP interop w. WM, Apache, SOAP4R
> Doug Davis wrote:
> >
> > Yup - seems like it would be needed for the system to be complete.
> > More of a java question - but how would we do it w/o threads?
> - Sam Ruby

View raw message