I'm reading through WCF Facility code and adding doco, currently about
wcf policies:
http://stw.castleproject.org/Windsor.WCF-Facility-Policies.ashx
http://stw.castleproject.org/Windsor.WCF-Facility-Refresh-Channel-Policy.ashx
http://stw.castleproject.org/Windsor.WCF-Facility-Channel-Action-Policy.ashx
I'm not really sure I see value in having this separation for different
kinds of policies. Why can't refresh channel policy be part of the same
pipeline as channel action policy?
We could do:
Refresh channel -> Circuit breaker -> Retry call -> (call)
pipeline like this, and have it as part of one chain of responsibility,
similar to how DynamicProxy interceptors are called, but crafted for
this specific usage and with no limitation as to how many times
Proceed() can be called (so that Retry call policy can work properly).
That would be pretty similar to how ExtendedHandler and
IResolveExtension/IReleaseExtensions work in Windsor:
http://github.com/castleproject/Castle.InversionOfControl/blob/master/src/Castle.Windsor/MicroKernel/Handlers/ExtendedHandler.cs
Thoughts? Ideas?
--
You received this message because you are subscribed to the Google Groups "Castle
Project Development List" 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-devel?hl=en.
