I have posted this question once back in July, but never got an answer.
Let's try again:
It seems webservices proxy Timeout is triggered not by elapse of time, but
the difference between the soap message timestamp and the server time. For
instance:
I've a rich client calling a webservices method. If I forward my client
machine system clock by 15 minutes, and set my webservice Timeout parameter
to 5 minutes, the call will fail immediately and receive a "Message Expired"
error. In another word, if my client and server aren't in sync with time,
webservices will throw an exception every times.
Can someone verifies this?
Thanks.
Bill Sun
--
"At school I never minded the lessons. I just resented having to work
terribly hard at playing." – John Mortimer 1923.
Let's try again:
It seems webservices proxy Timeout is triggered not by elapse of time, but
the difference between the soap message timestamp and the server time. For
instance:
I've a rich client calling a webservices method. If I forward my client
machine system clock by 15 minutes, and set my webservice Timeout parameter
to 5 minutes, the call will fail immediately and receive a "Message Expired"
error. In another word, if my client and server aren't in sync with time,
webservices will throw an exception every times.
Can someone verifies this?
Thanks.
Bill Sun
--
"At school I never minded the lessons. I just resented having to work
terribly hard at playing." – John Mortimer 1923.