Re: Controlling request/response timeout per request handler?
Re: Controlling request/response timeout per request handler?
- Subject: Re: Controlling request/response timeout per request handler?
- From: Lachlan Deck <email@hidden>
- Date: Wed, 6 Jun 2007 12:19:24 +1000
On 06/06/2007, at 11:54 AM, Chuck Hill wrote:
You could probably do it you want to hack on the C code of the
woadaptor...
Where / how is it timing out? Uploads should not be a problem.
Either they get accumulated in the webserver and send over in one
blast, in which case the connect and receive should be quick, or
they get streamed to the woapp which should avoid this entirely.
Hmm. Okay, that's good to know. I sometimes get a socket timeout
error - but that's a startup timing issue usually. The client app
sets the stub's timeout to 1 hour so I was just wanting to make
certain that large uploads won't timeout.
Streaming the data would certainly be better.
Thanks.
You are not referring to session timeouts?
No.
On Jun 5, 2007, at 6:41 PM, Lachlan Deck wrote:
I realise that you can adjust the adaptor's request/response
timeout settings in Java Monitor (for the WODefaultAdaptor) - but
I'm wondering if it's possible to adjust the timeout depending on
the request handler?
I'm wondering about turning the timeout up significantly for
webservice uploads of binary data but accepting the default values
for other requests.
Any ideas or alternatives?
with regards,
--
Lachlan Deck
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden