I am implementing some web services to support a new standard for my
industry. Because of the way these web services are defined, there is the
possibility that a large amount of data can be sent in one call. In some
cases I would want to make sure that the web service timeout is long enough
to run to completion. In others it may be more beneficial to lower the
timeout so that large blocks of data can't be used.

My question is simply if the web service timeout can be controlled from
inside the web services such that any timeout specified by the calling client
can be overridden?
--
dayblue

I have a similar question. The conclusion I'm coming to is that it's
implemented the way it is in order put the onus on the client - if the client
sends a large chunk of data and doesn't give it enough time to complete, oh
well... it's their foot; they shot themselves, etc.

If you have control over both sides of the wire for your implementation,
consider doing what I think I'm going to do: add an explicit
"requestedTimeout" parameter to the method (with a reasonable default), and
if you decide on the server that too much time is being requested, go ahead
and timeout/return on your own.

But, I'm all ears if anyone else has a better solution!

"dayblue" wrote: