On Jan 6, 2012, at 12:08 PM, DoniG wrote:
> I think I'm beginning to get it now...
>
> Why the comment about "Perhaps some exponential backoff logic here"?
> I would think this is only executed once, since the intent is to only
> retry the call once on a time out.
It's not uncommon in high available situations to retry for a longer time
period. If thats the case,
exponential backoff simply increases the time between attempts. If you only
need 1 timeout, it would not be useful.
>
> Also, shouldn't the catch clause be:
>
> catch (TimeoutException)
> {
> wcfInvocation.Refresh().Proceed();
> }
>
If it is truely a timeout, then the channel is probably still open, but it
won't hurt to have a refresh just in case
> since the channel will be faulted from the TimeoutException?
>
> Thanks,
>
> Doni
>
> --
> You received this message because you are subscribed to the Google Groups
> "Castle Project Users" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/castle-project-users?hl=en.
>
--
You received this message because you are subscribed to the Google Groups
"Castle Project Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/castle-project-users?hl=en.
